Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e07e6a867b1a6c2b31f2acd1b8dec00bd1444e9bd1a9ca4e9d29fb7b95f3d573

Tx prefix hash: e681bdd0a751a9b00754ca39bf06e8df61de12808e72fa0b7df62bffc3c0d736
Tx public key: 83ef8685791df3a73bac060c3ec8895bc5130b7018ae071014d83afeec7005a4
Timestamp: 1705171546 Timestamp [UCT]: 2024-01-13 18:45:46 Age [y:d:h:m:s]: 01:344:06:31:47
Block: 934601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 504929 RingCT/type: yes/0
Extra: 0183ef8685791df3a73bac060c3ec8895bc5130b7018ae071014d83afeec7005a402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11a5b30d49b315150d86fe0106737eec27fdfb783f49b96c4699159ba7729dc1 0.600000000000 1392615 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": 934611, "vin": [ { "gen": { "height": 934601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11a5b30d49b315150d86fe0106737eec27fdfb783f49b96c4699159ba7729dc1" } } ], "extra": [ 1, 131, 239, 134, 133, 121, 29, 243, 167, 59, 172, 6, 12, 62, 200, 137, 91, 197, 19, 11, 112, 24, 174, 7, 16, 20, 216, 58, 254, 236, 112, 5, 164, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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