Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc3dc7b6cd6b5c31ea52d7a3f92e0e22e0844bfd78f956b9a1dd2edfc9e4ddc0

Tx prefix hash: 5f3f8db7509da2cd1db77f5355a9fee865b244627ea1cad4473e97c1015a5c43
Tx public key: 2913434c9cbdca67046960fc95b47efa9b3722a3b950d6101a5e053694424aa4
Timestamp: 1718559899 Timestamp [UCT]: 2024-06-16 17:44:59 Age [y:d:h:m:s]: 00:208:20:58:40
Block: 1045633 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149460 RingCT/type: yes/0
Extra: 012913434c9cbdca67046960fc95b47efa9b3722a3b950d6101a5e053694424aa402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f14ca3a92e4d380622c32f108437ad2e2b0d32ea01605cdb66654d944aec9481 0.600000000000 1515256 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": 1045643, "vin": [ { "gen": { "height": 1045633 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f14ca3a92e4d380622c32f108437ad2e2b0d32ea01605cdb66654d944aec9481" } } ], "extra": [ 1, 41, 19, 67, 76, 156, 189, 202, 103, 4, 105, 96, 252, 149, 180, 126, 250, 155, 55, 34, 163, 185, 80, 214, 16, 26, 94, 5, 54, 148, 66, 74, 164, 2, 17, 0, 0, 0, 1, 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