Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37a32848bde88b8780d639dbb392db1614f8e70bbf68bb9187ecbebd86053fef

Tx prefix hash: a9692ee7b7259edefdae904ab4aafc6b0e0dec858e2b78172dafeff2450ff9a6
Tx public key: 067a5fcc85d15b7dbfbd809575756a85c68d9fb43986483b3df6f6e6a398a2ff
Timestamp: 1706461586 Timestamp [UCT]: 2024-01-28 17:06:26 Age [y:d:h:m:s]: 01:073:12:14:31
Block: 945293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313625 RingCT/type: yes/0
Extra: 01067a5fcc85d15b7dbfbd809575756a85c68d9fb43986483b3df6f6e6a398a2ff02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6634019d46073c95491fbeec44e8dcdc7e0127c06d3cdc5ce6f9e81d1c534095 0.600000000000 1403605 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": 945303, "vin": [ { "gen": { "height": 945293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6634019d46073c95491fbeec44e8dcdc7e0127c06d3cdc5ce6f9e81d1c534095" } } ], "extra": [ 1, 6, 122, 95, 204, 133, 209, 91, 125, 191, 189, 128, 149, 117, 117, 106, 133, 198, 141, 159, 180, 57, 134, 72, 59, 61, 246, 246, 230, 163, 152, 162, 255, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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