Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3011c1249f3628eee9daa450bca740c8395aedb2ad81f299fc757ec9b5d1bd54

Tx prefix hash: 07c45745cb7dbf364dcf759a5b9714c861c0d35cefbf0f4e442d6a5d629393fc
Tx public key: d504969f6b964cd33a1cd84c35f7182dd1a97780a007865367f319f992871d00
Timestamp: 1697057801 Timestamp [UCT]: 2023-10-11 20:56:41 Age [y:d:h:m:s]: 02:110:13:51:14
Block: 867561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 598571 RingCT/type: yes/0
Extra: 01d504969f6b964cd33a1cd84c35f7182dd1a97780a007865367f319f992871d000211000000074b8f5122000000000000000000

1 output(s) for total of 0.819238391000 dcy

stealth address amount amount idx
00: 2b247467dd0291edb80db0dabb84591beb43fb4a401326d50d8d2b363d6b193e 0.819238391000 1322253 of 0

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": 867571, "vin": [ { "gen": { "height": 867561 } } ], "vout": [ { "amount": 819238391, "target": { "key": "2b247467dd0291edb80db0dabb84591beb43fb4a401326d50d8d2b363d6b193e" } } ], "extra": [ 1, 213, 4, 150, 159, 107, 150, 76, 211, 58, 28, 216, 76, 53, 247, 24, 45, 209, 169, 119, 128, 160, 7, 134, 83, 103, 243, 25, 249, 146, 135, 29, 0, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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