Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b67379effe16d440eda1133e139b8a1ad8a43d74aa5494e8b9a8ed65c5c15c3d

Tx prefix hash: 63893c8f657635dd05fdf6b97c07cd3cc446fedbcef9f825f3edb9a940aacce6
Tx public key: 7b180ae759f68561ab37539a96f0d55596ff5e01f767b5a117cc4de2c70aaadc
Timestamp: 1703233602 Timestamp [UCT]: 2023-12-22 08:26:42 Age [y:d:h:m:s]: 01:034:02:57:10
Block: 918553 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285694 RingCT/type: yes/0
Extra: 017b180ae759f68561ab37539a96f0d55596ff5e01f767b5a117cc4de2c70aaadc02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 967824f98d69dddf851d821aa5067a7a916df9e130ce3c3e01d582ec8f6513ca 0.600000000000 1376199 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": 918563, "vin": [ { "gen": { "height": 918553 } } ], "vout": [ { "amount": 600000000, "target": { "key": "967824f98d69dddf851d821aa5067a7a916df9e130ce3c3e01d582ec8f6513ca" } } ], "extra": [ 1, 123, 24, 10, 231, 89, 246, 133, 97, 171, 55, 83, 154, 150, 240, 213, 85, 150, 255, 94, 1, 247, 103, 181, 161, 23, 204, 77, 226, 199, 10, 170, 220, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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