Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdfb1018b9ea0c06ba9e7c8b1f42ca0fbc1b4f2d130ce6a7e67b26befb4a08fe

Tx prefix hash: a4b64afbc5e24845d6310f2e656fe95efe2b0d46603741eae5d5bae019c85b1f
Tx public key: 49123160119e23827cb2fcb77e51f7b90710cf1eb371bb735482ec14190bdc49
Timestamp: 1707449071 Timestamp [UCT]: 2024-02-09 03:24:31 Age [y:d:h:m:s]: 00:318:03:04:21
Block: 953495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227793 RingCT/type: yes/0
Extra: 0149123160119e23827cb2fcb77e51f7b90710cf1eb371bb735482ec14190bdc4902110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 644b1de09fe08f342c91985a3a2d0b7816b59cb464837814743be681aadf272a 0.600000000000 1412711 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": 953505, "vin": [ { "gen": { "height": 953495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "644b1de09fe08f342c91985a3a2d0b7816b59cb464837814743be681aadf272a" } } ], "extra": [ 1, 73, 18, 49, 96, 17, 158, 35, 130, 124, 178, 252, 183, 126, 81, 247, 185, 7, 16, 207, 30, 179, 113, 187, 115, 84, 130, 236, 20, 25, 11, 220, 73, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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