Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9682a215c8a7d3ceef3b0a62461a2102e55b4c55326c268cf08b4f700efe6012

Tx prefix hash: 38dd8204ebc4836be0cb166fb8bcbfd8d4e6677f33a995ecff1c8fca4a754311
Tx public key: bc4534de90cebb9576fa0d13b1cbe145edcf2d7440d0ac2ec9c17105f1a281a5
Timestamp: 1712314474 Timestamp [UCT]: 2024-04-05 10:54:34 Age [y:d:h:m:s]: 01:064:03:01:08
Block: 993814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306862 RingCT/type: yes/0
Extra: 01bc4534de90cebb9576fa0d13b1cbe145edcf2d7440d0ac2ec9c17105f1a281a50211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66fcb48e6f1f65b55e72e8c79963cc56ead477bfe5dbeecea7db1320f9fb5e11 0.600000000000 1454202 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": 993824, "vin": [ { "gen": { "height": 993814 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66fcb48e6f1f65b55e72e8c79963cc56ead477bfe5dbeecea7db1320f9fb5e11" } } ], "extra": [ 1, 188, 69, 52, 222, 144, 206, 187, 149, 118, 250, 13, 19, 177, 203, 225, 69, 237, 207, 45, 116, 64, 208, 172, 46, 201, 193, 113, 5, 241, 162, 129, 165, 2, 17, 0, 0, 0, 3, 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