Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcfed2bc91724447c83e27ac26a313b0306c147ed99097ce8f5c46ba3a3cdce5

Tx prefix hash: 88f123db6debaca3d6bf9a04269290149e932f0c6ddb662cbd0559eae855efee
Tx public key: b1f9cb24f7d0c3511bc8342bec92807b7b1ac6829a79f692b690835512aeba12
Timestamp: 1751582406 Timestamp [UCT]: 2025-07-03 22:40:06 Age [y:d:h:m:s]: 00:128:23:25:09
Block: 1318218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90440 RingCT/type: yes/0
Extra: 01b1f9cb24f7d0c3511bc8342bec92807b7b1ac6829a79f692b690835512aeba120211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2a89420fede093cb6752152ff5b5f76b9ea1b54b0df0ecb102f6143251004f6 0.600000000000 1805895 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": 1318228, "vin": [ { "gen": { "height": 1318218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2a89420fede093cb6752152ff5b5f76b9ea1b54b0df0ecb102f6143251004f6" } } ], "extra": [ 1, 177, 249, 203, 36, 247, 208, 195, 81, 27, 200, 52, 43, 236, 146, 128, 123, 123, 26, 198, 130, 154, 121, 246, 146, 182, 144, 131, 85, 18, 174, 186, 18, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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