Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9d6035e2a0160355d34bcab07a36759323cec18c9d185c22ad816cd201e7441

Tx prefix hash: 6215fc6a37da6a340d792da9775f0d9e5493b6877a5c08c6d86c7c2154b7ea3e
Tx public key: 9a7db78d73874a5079f494bf4476260f8b2ec2ef47a7dc0867f8d9b90ad461a5
Timestamp: 1730370253 Timestamp [UCT]: 2024-10-31 10:24:13 Age [y:d:h:m:s]: 00:213:10:43:53
Block: 1143459 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152417 RingCT/type: yes/0
Extra: 019a7db78d73874a5079f494bf4476260f8b2ec2ef47a7dc0867f8d9b90ad461a5021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ed2c5519fedeac0c92822cd8a8ee71b2dbcd2d63a352fad91ba7c547ba3631e 0.600000000000 1627338 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": 1143469, "vin": [ { "gen": { "height": 1143459 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ed2c5519fedeac0c92822cd8a8ee71b2dbcd2d63a352fad91ba7c547ba3631e" } } ], "extra": [ 1, 154, 125, 183, 141, 115, 135, 74, 80, 121, 244, 148, 191, 68, 118, 38, 15, 139, 46, 194, 239, 71, 167, 220, 8, 103, 248, 217, 185, 10, 212, 97, 165, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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