Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdbd11c3e5a6dfbe86e54e02d50bb7662b78c59a246cd73cda857086d35f80f6

Tx prefix hash: 35575b0eb5ebce1224e370a0c2b6283092b5418864b5560dac3712368e8d0ecd
Tx public key: 0e8daf95a3c0cf747b993e21118bdde28a1e63106f09d425b1e74e43828f68fe
Timestamp: 1713619596 Timestamp [UCT]: 2024-04-20 13:26:36 Age [y:d:h:m:s]: 01:024:15:34:45
Block: 1004644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278588 RingCT/type: yes/0
Extra: 010e8daf95a3c0cf747b993e21118bdde28a1e63106f09d425b1e74e43828f68fe0211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90f9d80843be2d5dd5b26250e8ced73b0115d4dd147740eb26e2879f97f4df8f 0.600000000000 1465214 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": 1004654, "vin": [ { "gen": { "height": 1004644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90f9d80843be2d5dd5b26250e8ced73b0115d4dd147740eb26e2879f97f4df8f" } } ], "extra": [ 1, 14, 141, 175, 149, 163, 192, 207, 116, 123, 153, 62, 33, 17, 139, 221, 226, 138, 30, 99, 16, 111, 9, 212, 37, 177, 231, 78, 67, 130, 143, 104, 254, 2, 17, 0, 0, 0, 4, 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