Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf1f420c73640cd85f714f1611e39e74f04d8333477ec4237124c86c7c408cd7

Tx prefix hash: 992c43e46c305027e54e81eaca316f9b11cfbc720f1c75222d43d51b2e219955
Tx public key: 8edbb439b92b6ef077aa43f1a91a4887fb995dcefd10ddfcfae5497a6bc32d3c
Timestamp: 1755022802 Timestamp [UCT]: 2025-08-12 18:20:02 Age [y:d:h:m:s]: 00:106:23:40:41
Block: 1345603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75820 RingCT/type: yes/0
Extra: 018edbb439b92b6ef077aa43f1a91a4887fb995dcefd10ddfcfae5497a6bc32d3c021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2281576975dd501704a8bcd94ac25a2a0b8f9666c2d6b3d1281e892eb657f402 0.600000000000 1833498 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": 1345613, "vin": [ { "gen": { "height": 1345603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2281576975dd501704a8bcd94ac25a2a0b8f9666c2d6b3d1281e892eb657f402" } } ], "extra": [ 1, 142, 219, 180, 57, 185, 43, 110, 240, 119, 170, 67, 241, 169, 26, 72, 135, 251, 153, 93, 206, 253, 16, 221, 252, 250, 229, 73, 122, 107, 195, 45, 60, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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