Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 418229cd54767b181c7d8d25c6993268ac289263c6e6fc24cb8c468808003790

Tx prefix hash: 9e2a2b243a2f9e2c5ca19060594cb84754e125f94ef801f0ba7697a0cd8bde14
Tx public key: 2e273284271add1fa4e2d3b2372c2e1094342ccee6bd1458e5cf691beb1f5a02
Timestamp: 1731083517 Timestamp [UCT]: 2024-11-08 16:31:57 Age [y:d:h:m:s]: 00:206:06:19:41
Block: 1149362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147285 RingCT/type: yes/0
Extra: 012e273284271add1fa4e2d3b2372c2e1094342ccee6bd1458e5cf691beb1f5a02021100000003e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4187fd6cd339eaad5b26e4bfbcca6683b33fcd801c30f6f53336109849c4847 0.600000000000 1634425 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": 1149372, "vin": [ { "gen": { "height": 1149362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4187fd6cd339eaad5b26e4bfbcca6683b33fcd801c30f6f53336109849c4847" } } ], "extra": [ 1, 46, 39, 50, 132, 39, 26, 221, 31, 164, 226, 211, 178, 55, 44, 46, 16, 148, 52, 44, 206, 230, 189, 20, 88, 229, 207, 105, 27, 235, 31, 90, 2, 2, 17, 0, 0, 0, 3, 228, 220, 144, 9, 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