Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be5af083644051ffd11a155649dc767bf1c2100047ef34704b0beae8ef084f47

Tx prefix hash: 30610d4e39adba03f27499420a4a1acc2c76eed9f5c716a27ad09f36577fdb85
Tx public key: 2ba8c612ca2d9632f643000774f71c4710ce2a3fe6663d8ff8071e64b0cc4ac3
Timestamp: 1694795430 Timestamp [UCT]: 2023-09-15 16:30:30 Age [y:d:h:m:s]: 01:214:15:27:08
Block: 848785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414496 RingCT/type: yes/0
Extra: 012ba8c612ca2d9632f643000774f71c4710ce2a3fe6663d8ff8071e64b0cc4ac302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.945416126000 dcy

stealth address amount amount idx
00: 36dfcb8fd2334d21f1c51b43c9fb7661743b75bb2ba4bf1f6617e44cbe7c69d5 0.945416126000 1302411 of 0

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": 848795, "vin": [ { "gen": { "height": 848785 } } ], "vout": [ { "amount": 945416126, "target": { "key": "36dfcb8fd2334d21f1c51b43c9fb7661743b75bb2ba4bf1f6617e44cbe7c69d5" } } ], "extra": [ 1, 43, 168, 198, 18, 202, 45, 150, 50, 246, 67, 0, 7, 116, 247, 28, 71, 16, 206, 42, 63, 230, 102, 61, 143, 248, 7, 30, 100, 176, 204, 74, 195, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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