Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e1ec099e0082286df0f4d6af8f2d0aef259a38472ba599d99004fa98be30e72

Tx prefix hash: d0938e03790679551c9670792bf22271d4f8bc52b0653164840d8b048d2e2530
Tx public key: 02e1f83dc98ad875e6d913c5adf8328f3a27a5650552c8b4fb77d243fe016aef
Timestamp: 1722452452 Timestamp [UCT]: 2024-07-31 19:00:52 Age [y:d:h:m:s]: 00:266:07:40:40
Block: 1077877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190259 RingCT/type: yes/0
Extra: 0102e1f83dc98ad875e6d913c5adf8328f3a27a5650552c8b4fb77d243fe016aef02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 241cdfc385317548d719e096e3f4f074d19cddde260eb50d70eea8641b553c36 0.600000000000 1550432 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": 1077887, "vin": [ { "gen": { "height": 1077877 } } ], "vout": [ { "amount": 600000000, "target": { "key": "241cdfc385317548d719e096e3f4f074d19cddde260eb50d70eea8641b553c36" } } ], "extra": [ 1, 2, 225, 248, 61, 201, 138, 216, 117, 230, 217, 19, 197, 173, 248, 50, 143, 58, 39, 165, 101, 5, 82, 200, 180, 251, 119, 210, 67, 254, 1, 106, 239, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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