Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82c247eebb74964f60b483a1a3b831303d64c0171998a114678bde9e8d44935f

Tx prefix hash: 5bad4d37b96c9a39a7da2ce512f5f8c6e46e67ac66e57a324b1799d757453ef1
Tx public key: fee8125c7d4b803d1049dd906156fd4ba4178f55fcf311435cad4250a7e817b6
Timestamp: 1735938893 Timestamp [UCT]: 2025-01-03 21:14:53 Age [y:d:h:m:s]: 00:304:10:29:42
Block: 1189573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215073 RingCT/type: yes/0
Extra: 01fee8125c7d4b803d1049dd906156fd4ba4178f55fcf311435cad4250a7e817b60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea7ea34b7cd3d3654af2d56da8ae4b9bfb2e087a664b4dabfff12de0a2076997 0.600000000000 1676084 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": 1189583, "vin": [ { "gen": { "height": 1189573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea7ea34b7cd3d3654af2d56da8ae4b9bfb2e087a664b4dabfff12de0a2076997" } } ], "extra": [ 1, 254, 232, 18, 92, 125, 75, 128, 61, 16, 73, 221, 144, 97, 86, 253, 75, 164, 23, 143, 85, 252, 243, 17, 67, 92, 173, 66, 80, 167, 232, 23, 182, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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