Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a13321881b79cddc2e8b7c86f8fa0af7a8df776a24eb8a4e237688712c2ba2c

Tx prefix hash: 070b55ba7a8365ea730cad5f4b32c7ab7d2df4c28bea27d045cc2ba170d9bfa1
Tx public key: 183205494c2ab5926eefaa74301e81f962f965a8d78f9265288df4a74bb360a1
Timestamp: 1713563298 Timestamp [UCT]: 2024-04-19 21:48:18 Age [y:d:h:m:s]: 00:307:20:25:00
Block: 1004172 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220055 RingCT/type: yes/0
Extra: 01183205494c2ab5926eefaa74301e81f962f965a8d78f9265288df4a74bb360a10211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fe374e0f0ff991b8c722a4bb2f5a3b9379cca9d7cd3249974a39fca24fa05ce 0.600000000000 1464740 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": 1004182, "vin": [ { "gen": { "height": 1004172 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fe374e0f0ff991b8c722a4bb2f5a3b9379cca9d7cd3249974a39fca24fa05ce" } } ], "extra": [ 1, 24, 50, 5, 73, 76, 42, 181, 146, 110, 239, 170, 116, 48, 30, 129, 249, 98, 249, 101, 168, 215, 143, 146, 101, 40, 141, 244, 167, 75, 179, 96, 161, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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