Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 490d7bbcf29495bb3d7d01cb4ec878128313f12107e6b2c5ff73270eb7c8e0c5

Tx prefix hash: b12f78edc609a4bacb02ebf206e1d5b95aa7063cc55d27b905eab52ab0a73cd2
Tx public key: 1a8d895242266db6c35e0b2cd82b24ecd0298420dbf8adce7be136af5e75f505
Timestamp: 1764880286 Timestamp [UCT]: 2025-12-04 20:31:26 Age [y:d:h:m:s]: 00:054:22:32:36
Block: 1426520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 39141 RingCT/type: yes/0
Extra: 011a8d895242266db6c35e0b2cd82b24ecd0298420dbf8adce7be136af5e75f505021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d65c31b5dc838d3195e6120f3413989b947503e2ec5f7fe282cf725958f049c 0.600000000000 1915211 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": 1426530, "vin": [ { "gen": { "height": 1426520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d65c31b5dc838d3195e6120f3413989b947503e2ec5f7fe282cf725958f049c" } } ], "extra": [ 1, 26, 141, 137, 82, 66, 38, 109, 182, 195, 94, 11, 44, 216, 43, 36, 236, 208, 41, 132, 32, 219, 248, 173, 206, 123, 225, 54, 175, 94, 117, 245, 5, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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