Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08d4a8a6625a185e192e0a7beae04b8f288fc622777092e67672e578e89b7247

Tx prefix hash: 6103ee4a115a130f7ae269fa9b32b6a540c79d60be9fe9e0aa8f4bd62ca9d420
Tx public key: 26b7cf93c1a704cf89b480a8ec5d562593a4490dec62d79f214772f67f78245f
Timestamp: 1762450318 Timestamp [UCT]: 2025-11-06 17:31:58 Age [y:d:h:m:s]: 00:062:17:14:54
Block: 1406348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44930 RingCT/type: yes/0
Extra: 0126b7cf93c1a704cf89b480a8ec5d562593a4490dec62d79f214772f67f78245f021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91afceca615a16126a7bc563d8218bf7c3d094a2205697876d761ac678c271f9 0.600000000000 1894731 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": 1406358, "vin": [ { "gen": { "height": 1406348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91afceca615a16126a7bc563d8218bf7c3d094a2205697876d761ac678c271f9" } } ], "extra": [ 1, 38, 183, 207, 147, 193, 167, 4, 207, 137, 180, 128, 168, 236, 93, 86, 37, 147, 164, 73, 13, 236, 98, 215, 159, 33, 71, 114, 246, 127, 120, 36, 95, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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