Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d4f7e60486fb887d7063a08c8ee42eb7b4561679a25e1e8895b3aebe07fbf29

Tx prefix hash: 373538295e35fa1fda400c4a4c7953a8f67279ff07385c93d0efc2a316d7ecfb
Tx public key: 9ebbf540bdc77d47846bcf8481b3547fc6539716b6d1c7d402d00731de9a47ba
Timestamp: 1726493268 Timestamp [UCT]: 2024-09-16 13:27:48 Age [y:d:h:m:s]: 00:203:18:08:21
Block: 1111389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145440 RingCT/type: yes/0
Extra: 019ebbf540bdc77d47846bcf8481b3547fc6539716b6d1c7d402d00731de9a47ba02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e58d07c2b6fef3d618ebcac8f02a09da5b57c1ef6e1d59356a43993ea57718ae 0.600000000000 1590328 of 15

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": 1111399, "vin": [ { "gen": { "height": 1111389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e58d07c2b6fef3d618ebcac8f02a09da5b57c1ef6e1d59356a43993ea57718ae" } } ], "extra": [ 1, 158, 187, 245, 64, 189, 199, 125, 71, 132, 107, 207, 132, 129, 179, 84, 127, 198, 83, 151, 22, 182, 209, 199, 212, 2, 208, 7, 49, 222, 154, 71, 186, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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