Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ca21060bf3ef11db8ce2f8be16c50e7e86fccb9877695d0f8d9ffed63b5d1ad

Tx prefix hash: 19213ef6dbc28f9889f8fa4cf01a4164e9647bd99efc94a251702f2b1b952871
Tx public key: 979dc7bec8ed50d7ddf4593f59336f02c3765e1e3ecc5ed6f70698e4b3d942f7
Timestamp: 1712917709 Timestamp [UCT]: 2024-04-12 10:28:29 Age [y:d:h:m:s]: 01:012:00:17:45
Block: 998815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269567 RingCT/type: yes/0
Extra: 01979dc7bec8ed50d7ddf4593f59336f02c3765e1e3ecc5ed6f70698e4b3d942f702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 62520b31cf12a55bb346b11d38ab4c4c9894f08ded9fa44f9e50d18171172714 0.600000000000 1459279 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": 998825, "vin": [ { "gen": { "height": 998815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "62520b31cf12a55bb346b11d38ab4c4c9894f08ded9fa44f9e50d18171172714" } } ], "extra": [ 1, 151, 157, 199, 190, 200, 237, 80, 215, 221, 244, 89, 63, 89, 51, 111, 2, 195, 118, 94, 30, 62, 204, 94, 214, 247, 6, 152, 228, 179, 217, 66, 247, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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