Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1ce45bb3ccf1ca2b8fa9864df81224be144bf458985add659837f704f657d68

Tx prefix hash: be282eb7281a141348fb0417012a37da542b2e7b4dcf9cc3b4b97f7c833e9de7
Tx public key: 7e3df0673416ed7d94162fa8e16467c9e5dc423c820554c88c26432d40d4d60a
Timestamp: 1712727431 Timestamp [UCT]: 2024-04-10 05:37:11 Age [y:d:h:m:s]: 00:164:07:01:51
Block: 997237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117716 RingCT/type: yes/0
Extra: 017e3df0673416ed7d94162fa8e16467c9e5dc423c820554c88c26432d40d4d60a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 024cb27d20dd493eeda772887116bd78bb9b90f9f2fa362e41484f0e92d89097 0.600000000000 1457667 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": 997247, "vin": [ { "gen": { "height": 997237 } } ], "vout": [ { "amount": 600000000, "target": { "key": "024cb27d20dd493eeda772887116bd78bb9b90f9f2fa362e41484f0e92d89097" } } ], "extra": [ 1, 126, 61, 240, 103, 52, 22, 237, 125, 148, 22, 47, 168, 225, 100, 103, 201, 229, 220, 66, 60, 130, 5, 84, 200, 140, 38, 67, 45, 64, 212, 214, 10, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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