Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f6f410cff9b335171d2ec684e15344e95df7c262c1e7fe0e18e84d1c42d6258

Tx prefix hash: 5acec42ac9f6e14132946d3981d36061a020205b359024cc7f43cd7dede1834a
Tx public key: c5dcceed6a188cf14ae135db49e477d6a68931b7f3e979fcc3d9a0f388f39f1f
Timestamp: 1705696650 Timestamp [UCT]: 2024-01-19 20:37:30 Age [y:d:h:m:s]: 00:357:11:21:24
Block: 938950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 255939 RingCT/type: yes/0
Extra: 01c5dcceed6a188cf14ae135db49e477d6a68931b7f3e979fcc3d9a0f388f39f1f0211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ae85f14fbc85e65766c017d2d83cd5c6d326e26c77bf9e5d63bdf0ef0e54d3d 0.600000000000 1397034 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": 938960, "vin": [ { "gen": { "height": 938950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ae85f14fbc85e65766c017d2d83cd5c6d326e26c77bf9e5d63bdf0ef0e54d3d" } } ], "extra": [ 1, 197, 220, 206, 237, 106, 24, 140, 241, 74, 225, 53, 219, 73, 228, 119, 214, 166, 137, 49, 183, 243, 233, 121, 252, 195, 217, 160, 243, 136, 243, 159, 31, 2, 17, 0, 0, 0, 16, 122, 156, 244, 199, 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