Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e02b4debeba810cc7858eb8bd85ab583ca24b3186cb55e6f67a64307816c847

Tx prefix hash: 2aa357ece235f314b4341a27cb849b8bc6a83c75a92004b08c8ee24123d35ff1
Tx public key: 33c26f572cda14cb46a3dea377357ee988c8d69e5100a4d1320a38d9c0705f42
Timestamp: 1709160791 Timestamp [UCT]: 2024-02-28 22:53:11 Age [y:d:h:m:s]: 01:035:22:48:02
Block: 967701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286690 RingCT/type: yes/0
Extra: 0133c26f572cda14cb46a3dea377357ee988c8d69e5100a4d1320a38d9c0705f4202110000000c7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb1e3f19292ae2f921b74694108f2e279bc7b0a78c51292315cdeb02a874b366 0.600000000000 1427484 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": 967711, "vin": [ { "gen": { "height": 967701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb1e3f19292ae2f921b74694108f2e279bc7b0a78c51292315cdeb02a874b366" } } ], "extra": [ 1, 51, 194, 111, 87, 44, 218, 20, 203, 70, 163, 222, 163, 119, 53, 126, 233, 136, 200, 214, 158, 81, 0, 164, 209, 50, 10, 56, 217, 192, 112, 95, 66, 2, 17, 0, 0, 0, 12, 122, 156, 244, 199, 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