Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2a23466a6ecbd1953c79540162892dba436b544057bdc6ca816a13b0c66a269

Tx prefix hash: f9f8ef75c2877490bd85586087bacb34e92d2b80a2c9f2d3ca8285bba10d6e43
Tx public key: 1fecf796154c74c9bdf5897b9fd63ed6a8ae824ed3d544105aeb3a22edbdc194
Timestamp: 1717948505 Timestamp [UCT]: 2024-06-09 15:55:05 Age [y:d:h:m:s]: 01:151:22:02:49
Block: 1040549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 367142 RingCT/type: yes/0
Extra: 011fecf796154c74c9bdf5897b9fd63ed6a8ae824ed3d544105aeb3a22edbdc1940211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b097e399664a0335173028bb0541760c703509b07fba8ff9c40a692e93f884f9 0.600000000000 1509206 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": 1040559, "vin": [ { "gen": { "height": 1040549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b097e399664a0335173028bb0541760c703509b07fba8ff9c40a692e93f884f9" } } ], "extra": [ 1, 31, 236, 247, 150, 21, 76, 116, 201, 189, 245, 137, 123, 159, 214, 62, 214, 168, 174, 130, 78, 211, 213, 68, 16, 90, 235, 58, 34, 237, 189, 193, 148, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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