Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf67460e0849bd5e68dfd2f3a284f63176d4b1481aa545f50525a4d65060de43

Tx prefix hash: 0c75f3a6baa7792a06921367509dff04112bdb6071817b15c94e3218f164f89f
Tx public key: 3a23501d336254d6b30457029db3bb3703c564e3b0dd5e6b36504a938454c65f
Timestamp: 1720637199 Timestamp [UCT]: 2024-07-10 18:46:39 Age [y:d:h:m:s]: 01:125:02:18:34
Block: 1062845 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347919 RingCT/type: yes/0
Extra: 013a23501d336254d6b30457029db3bb3703c564e3b0dd5e6b36504a938454c65f02110000001191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7492625fdf52cf915372e50ee3795add82b2dd3f49e5f6f8c6e35b15f9cdefa 0.600000000000 1533356 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": 1062855, "vin": [ { "gen": { "height": 1062845 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7492625fdf52cf915372e50ee3795add82b2dd3f49e5f6f8c6e35b15f9cdefa" } } ], "extra": [ 1, 58, 35, 80, 29, 51, 98, 84, 214, 179, 4, 87, 2, 157, 179, 187, 55, 3, 197, 100, 227, 176, 221, 94, 107, 54, 80, 74, 147, 132, 84, 198, 95, 2, 17, 0, 0, 0, 17, 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