Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b28376c008d5b0da3cc7aed76c334e33658435d3145094b542c09d891349a29b

Tx prefix hash: 7ccf49cfaaa16f2f44d0c20645a6cac6f31599eb2427b75e785c03fb6eb02e2a
Tx public key: db22aecb8dcf32d165fe9a23b1a731f8b5aad1b8733b2a826d1557d6795466b6
Timestamp: 1754817552 Timestamp [UCT]: 2025-08-10 09:19:12 Age [y:d:h:m:s]: 00:102:18:44:49
Block: 1344047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72644 RingCT/type: yes/0
Extra: 01db22aecb8dcf32d165fe9a23b1a731f8b5aad1b8733b2a826d1557d6795466b6021100000003b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4e595bd6c0d4c17783793035467aab01f464b3ef5d77122be0a30f366534fcb7 0.600000000000 1831914 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": 1344057, "vin": [ { "gen": { "height": 1344047 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4e595bd6c0d4c17783793035467aab01f464b3ef5d77122be0a30f366534fcb7" } } ], "extra": [ 1, 219, 34, 174, 203, 141, 207, 50, 209, 101, 254, 154, 35, 177, 167, 49, 248, 181, 170, 209, 184, 115, 59, 42, 130, 109, 21, 87, 214, 121, 84, 102, 182, 2, 17, 0, 0, 0, 3, 178, 247, 132, 196, 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