Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9992edb0f8d8ff4009d54db9c621d59c4018a12df434de6f6871827f1e6335d7

Tx prefix hash: 1428ce0c5f1b6c434dd1d40c5165dc77e80f855eb52f1de6763d1a2277443f96
Tx public key: a18431e97839072aebd06570ea46a07afa8910307871100b87d9b6010d1c4c3a
Timestamp: 1715177563 Timestamp [UCT]: 2024-05-08 14:12:43 Age [y:d:h:m:s]: 00:290:14:25:18
Block: 1017588 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207672 RingCT/type: yes/0
Extra: 01a18431e97839072aebd06570ea46a07afa8910307871100b87d9b6010d1c4c3a0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dee67887c19fd9c115b9ccd3e00b460cfd4e0765a05984ea2271d251a79c48e9 0.600000000000 1481371 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": 1017598, "vin": [ { "gen": { "height": 1017588 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dee67887c19fd9c115b9ccd3e00b460cfd4e0765a05984ea2271d251a79c48e9" } } ], "extra": [ 1, 161, 132, 49, 233, 120, 57, 7, 42, 235, 208, 101, 112, 234, 70, 160, 122, 250, 137, 16, 48, 120, 113, 16, 11, 135, 217, 182, 1, 13, 28, 76, 58, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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