Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 215ca84294f9000574a1b958c9470aa1bc807ed535b7091f7dc3f5694cc39b18

Tx prefix hash: 344469b0774a5b6582d24182e92702fd02a8260a364584d3b38bc4af9362fa47
Tx public key: 86fbde5d0c6d6f767a953a05e0472747b2e3901042b937e23892bc27d45d544e
Timestamp: 1730526252 Timestamp [UCT]: 2024-11-02 05:44:12 Age [y:d:h:m:s]: 00:147:00:25:39
Block: 1144736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104907 RingCT/type: yes/0
Extra: 0186fbde5d0c6d6f767a953a05e0472747b2e3901042b937e23892bc27d45d544e0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 347c552dd68258fd0e409c0a7c2980ec48e7a675e59413aabfbb8ee51e0bf7da 0.600000000000 1629027 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": 1144746, "vin": [ { "gen": { "height": 1144736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "347c552dd68258fd0e409c0a7c2980ec48e7a675e59413aabfbb8ee51e0bf7da" } } ], "extra": [ 1, 134, 251, 222, 93, 12, 109, 111, 118, 122, 149, 58, 5, 224, 71, 39, 71, 178, 227, 144, 16, 66, 185, 55, 226, 56, 146, 188, 39, 212, 93, 84, 78, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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