Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652785420d465d0e2f765480a4865b89533a8de13eed0773ba7f5090edb3e499

Tx prefix hash: e6bd21d4da2b67dba3b00b470b48c84eb743ba692c28f4641b73cd2bb4474450
Tx public key: 5163b12e37e9d4876da2b64f3ffdbf803a39e44e19f139f8c594ba5c3bf09fb3
Timestamp: 1711766605 Timestamp [UCT]: 2024-03-30 02:43:25 Age [y:d:h:m:s]: 01:060:00:53:26
Block: 989311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303905 RingCT/type: yes/0
Extra: 015163b12e37e9d4876da2b64f3ffdbf803a39e44e19f139f8c594ba5c3bf09fb30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac7d78fddba953994e325825eb7a067c870a9610a35956b300ceb9e2bfd0d816 0.600000000000 1449606 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": 989321, "vin": [ { "gen": { "height": 989311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac7d78fddba953994e325825eb7a067c870a9610a35956b300ceb9e2bfd0d816" } } ], "extra": [ 1, 81, 99, 177, 46, 55, 233, 212, 135, 109, 162, 182, 79, 63, 253, 191, 128, 58, 57, 228, 78, 25, 241, 57, 248, 197, 148, 186, 92, 59, 240, 159, 179, 2, 17, 0, 0, 0, 2, 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