Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e53d63b76519911bffa2c7b7970c0d71ce9540184977b24616e80e88c60501ff

Tx prefix hash: 024a1d59059b991bf7c4d531265f18fc7f4cac3f276891d72a6419837fcd8639
Tx public key: 66215e85d08dfbc828521186c57df05264f74fa265f9db6124bfe7fe5c4bde22
Timestamp: 1701156569 Timestamp [UCT]: 2023-11-28 07:29:29 Age [y:d:h:m:s]: 01:345:14:45:49
Block: 901331 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 505896 RingCT/type: yes/0
Extra: 0166215e85d08dfbc828521186c57df05264f74fa265f9db6124bfe7fe5c4bde2202110000000575e3f0e9000000000000000000

1 output(s) for total of 0.633164006000 dcy

stealth address amount amount idx
00: 8a3de6007d065aaf9906e864aa1659bcba7738e2f6d873889f9f1c76ffe7ef44 0.633164006000 1357884 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": 901341, "vin": [ { "gen": { "height": 901331 } } ], "vout": [ { "amount": 633164006, "target": { "key": "8a3de6007d065aaf9906e864aa1659bcba7738e2f6d873889f9f1c76ffe7ef44" } } ], "extra": [ 1, 102, 33, 94, 133, 208, 141, 251, 200, 40, 82, 17, 134, 197, 125, 240, 82, 100, 247, 79, 162, 101, 249, 219, 97, 36, 191, 231, 254, 92, 75, 222, 34, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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