Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ba2e98f42c1b9721b14290d9362e4580458a069bdd121fcd0bc1e17d54e9723

Tx prefix hash: 195d7baf7c263922f9a79de11330581fdb898e8cc580b2cd499b30a05a294787
Tx public key: 7c64aca8e60a325519a349427a5c300eeb1f9bcf71c59e00b04517d4529253a1
Timestamp: 1702470286 Timestamp [UCT]: 2023-12-13 12:24:46 Age [y:d:h:m:s]: 01:179:12:32:56
Block: 912245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389462 RingCT/type: yes/0
Extra: 017c64aca8e60a325519a349427a5c300eeb1f9bcf71c59e00b04517d4529253a102110000000833af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65210f236b07db55c9fd192e932250dfee7e145b683f1dc6e96ae076b77a7bab 0.600000000000 1369471 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": 912255, "vin": [ { "gen": { "height": 912245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65210f236b07db55c9fd192e932250dfee7e145b683f1dc6e96ae076b77a7bab" } } ], "extra": [ 1, 124, 100, 172, 168, 230, 10, 50, 85, 25, 163, 73, 66, 122, 92, 48, 14, 235, 31, 155, 207, 113, 197, 158, 0, 176, 69, 23, 212, 82, 146, 83, 161, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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