Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d90f9323f178b1c7e26dd7ed32d7e5976ac841546073131d5ac10d1ff48dccfe

Tx prefix hash: 35d952c39c92329dc6eca995073721151a7233793f442415964d65de3f4827b7
Tx public key: 5df727a483841a28348b5197e0b140ba5519b4aebf231f25b935addb6140a51e
Timestamp: 1710696297 Timestamp [UCT]: 2024-03-17 17:24:57 Age [y:d:h:m:s]: 01:004:22:32:56
Block: 980438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 264503 RingCT/type: yes/0
Extra: 015df727a483841a28348b5197e0b140ba5519b4aebf231f25b935addb6140a51e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4b693ad2a59fa174e6eb051862ee2d9cec25f4198f532013fb5c284ea2ee0d4 0.600000000000 1440505 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": 980448, "vin": [ { "gen": { "height": 980438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4b693ad2a59fa174e6eb051862ee2d9cec25f4198f532013fb5c284ea2ee0d4" } } ], "extra": [ 1, 93, 247, 39, 164, 131, 132, 26, 40, 52, 139, 81, 151, 224, 177, 64, 186, 85, 25, 180, 174, 191, 35, 31, 37, 185, 53, 173, 219, 97, 64, 165, 30, 2, 17, 0, 0, 0, 1, 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