Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b678474ceb3bcbb2a7b1d223ca96b80de8b44f819ed891f8c4bf3fb13bd69ce9

Tx prefix hash: e1ba875d27edd3c70ebcf812bd16f9e0d14a8073a701fb23f07fc8d06e8a0058
Tx public key: 075b49f05edb2c1c5980f4d96680009c3a230e1f346d3707327306de757ceef0
Timestamp: 1714391134 Timestamp [UCT]: 2024-04-29 11:45:34 Age [y:d:h:m:s]: 00:327:15:28:11
Block: 1011053 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 234218 RingCT/type: yes/0
Extra: 01075b49f05edb2c1c5980f4d96680009c3a230e1f346d3707327306de757ceef00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 819267f70f41f67cd58c36a8b37c9a3a51e56b3a07b988dafeddf4cd8ab4a25a 0.600000000000 1473177 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": 1011063, "vin": [ { "gen": { "height": 1011053 } } ], "vout": [ { "amount": 600000000, "target": { "key": "819267f70f41f67cd58c36a8b37c9a3a51e56b3a07b988dafeddf4cd8ab4a25a" } } ], "extra": [ 1, 7, 91, 73, 240, 94, 219, 44, 28, 89, 128, 244, 217, 102, 128, 0, 156, 58, 35, 14, 31, 52, 109, 55, 7, 50, 115, 6, 222, 117, 124, 238, 240, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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