Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 436b19cb61d4307e2839f49354cad20ea03f4effc91976ad9f00e7258392c07f

Tx prefix hash: a46678c7be668cbef12a2f87699681c8bdad16c56a8a983fbec427339fa3f2a6
Tx public key: 61970761b93d20f014c0b3e4f2d5217703297920d0bb9b3c831d3892f35f2fd0
Timestamp: 1578980575 Timestamp [UCT]: 2020-01-14 05:42:55 Age [y:d:h:m:s]: 05:137:22:05:52
Block: 45155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1248778 RingCT/type: yes/0
Extra: 0161970761b93d20f014c0b3e4f2d5217703297920d0bb9b3c831d3892f35f2fd00211000000054ac5aa02000000000000000000

1 output(s) for total of 434.894164598000 dcy

stealth address amount amount idx
00: b51e7f4689654b5a8e2b03925587a9a5d427896a145d51e2f051a0da53d2c619 434.894164598000 82397 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 45165, "vin": [ { "gen": { "height": 45155 } } ], "vout": [ { "amount": 434894164598, "target": { "key": "b51e7f4689654b5a8e2b03925587a9a5d427896a145d51e2f051a0da53d2c619" } } ], "extra": [ 1, 97, 151, 7, 97, 185, 61, 32, 240, 20, 192, 179, 228, 242, 213, 33, 119, 3, 41, 121, 32, 208, 187, 155, 60, 131, 29, 56, 146, 243, 95, 47, 208, 2, 17, 0, 0, 0, 5, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8