Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 459693693e94b923ad506b8df3047046bf571da512f384ee8d12ef3b9031a51e

Tx prefix hash: 34c57d97ec963b7549c9a14eb1f76b5a87a497462cf4eafec5088d62943db536
Tx public key: c08041a2e1cb10358de3c2420b8404761059d728c6aeea9540829ed223a7a592
Timestamp: 1731694927 Timestamp [UCT]: 2024-11-15 18:22:07 Age [y:d:h:m:s]: 00:146:09:18:48
Block: 1154413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104459 RingCT/type: yes/0
Extra: 01c08041a2e1cb10358de3c2420b8404761059d728c6aeea9540829ed223a7a592021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51d9e7a51035fd6f4ae512afc03b215e2682cc4d2bd02d9551b6f95d41ff5524 0.600000000000 1640024 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": 1154423, "vin": [ { "gen": { "height": 1154413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51d9e7a51035fd6f4ae512afc03b215e2682cc4d2bd02d9551b6f95d41ff5524" } } ], "extra": [ 1, 192, 128, 65, 162, 225, 203, 16, 53, 141, 227, 194, 66, 11, 132, 4, 118, 16, 89, 215, 40, 198, 174, 234, 149, 64, 130, 158, 210, 35, 167, 165, 146, 2, 17, 0, 0, 0, 4, 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