Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8b50075cc635f363e000c59e82524b1c0d62911a95403cb67b328911ced247b

Tx prefix hash: bf646161dc67a9bef0f886c56a351b61ae0080d0d716278d2563842ac89fbc8e
Tx public key: 47202b9f279df2477d9914d4e1a2536640ed227a4943145f9cbc8735b034b3e3
Timestamp: 1751908045 Timestamp [UCT]: 2025-07-07 17:07:25 Age [y:d:h:m:s]: 00:128:03:57:48
Block: 1320747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90017 RingCT/type: yes/0
Extra: 0147202b9f279df2477d9914d4e1a2536640ed227a4943145f9cbc8735b034b3e30211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4c1da9c21bf0382b0e64b46730895d4c4c1b252e295a705b20c20a2b3968a63 0.600000000000 1808448 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": 1320757, "vin": [ { "gen": { "height": 1320747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4c1da9c21bf0382b0e64b46730895d4c4c1b252e295a705b20c20a2b3968a63" } } ], "extra": [ 1, 71, 32, 43, 159, 39, 157, 242, 71, 125, 153, 20, 212, 225, 162, 83, 102, 64, 237, 34, 122, 73, 67, 20, 95, 156, 188, 135, 53, 176, 52, 179, 227, 2, 17, 0, 0, 0, 2, 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