Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05e2f93b3ecbd791edccaaa71b515a178ad06c99faf674bfcd1a40b950714463

Tx prefix hash: 5eeba99303d35e910b08f6508929a84f62839dc3e2034d3bdecfdaf1e6270d04
Tx public key: 7918c9857ff4c64cb4b9a36b59b4f13a9511fde12873929e33a8e792f6788e02
Timestamp: 1736049928 Timestamp [UCT]: 2025-01-05 04:05:28 Age [y:d:h:m:s]: 00:075:13:30:49
Block: 1190487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53781 RingCT/type: yes/0
Extra: 017918c9857ff4c64cb4b9a36b59b4f13a9511fde12873929e33a8e792f6788e02021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34669d7c29eb1d5a1eeb3bd97ccf1fa834464f3a6b131d79ecc2b8444a81993b 0.600000000000 1677004 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": 1190497, "vin": [ { "gen": { "height": 1190487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34669d7c29eb1d5a1eeb3bd97ccf1fa834464f3a6b131d79ecc2b8444a81993b" } } ], "extra": [ 1, 121, 24, 201, 133, 127, 244, 198, 76, 180, 185, 163, 107, 89, 180, 241, 58, 149, 17, 253, 225, 40, 115, 146, 158, 51, 168, 231, 146, 246, 120, 142, 2, 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