Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c9e2917f6cd89620861e19aaecfc56e71b84f7a9e1b80d7f2efdee94118f348

Tx prefix hash: 69c153f48292af2cf4475e11b9c4c99836fb40f180932d897e61fc607988448f
Tx public key: 5430c9e0707a8a7d77fabb9a3f19e6ea2ff91cfe75ccd5ceabb008c38ae48688
Timestamp: 1722450583 Timestamp [UCT]: 2024-07-31 18:29:43 Age [y:d:h:m:s]: 00:259:00:43:46
Block: 1077864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185042 RingCT/type: yes/0
Extra: 015430c9e0707a8a7d77fabb9a3f19e6ea2ff91cfe75ccd5ceabb008c38ae4868802110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc4ac4d47fa5c33ef9a36ff64fe44fca8f86288637296bb6babe2cf4d56f3daf 0.600000000000 1550419 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": 1077874, "vin": [ { "gen": { "height": 1077864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc4ac4d47fa5c33ef9a36ff64fe44fca8f86288637296bb6babe2cf4d56f3daf" } } ], "extra": [ 1, 84, 48, 201, 224, 112, 122, 138, 125, 119, 250, 187, 154, 63, 25, 230, 234, 47, 249, 28, 254, 117, 204, 213, 206, 171, 176, 8, 195, 138, 228, 134, 136, 2, 17, 0, 0, 0, 9, 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