Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a51883fb88e4ebd2563af1834470fd8b723e4473f7438119bba9d994f1b8803

Tx prefix hash: 5fee3a2db9714805a94943721dd689e5b58c37bf160519b12a4b6e07fd43b84b
Tx public key: 523f52d8543d8821e833cb09de20573e5002c2d6ba0ec0df3477df76b8ef9a70
Timestamp: 1763033022 Timestamp [UCT]: 2025-11-13 11:23:42 Age [y:d:h:m:s]: 00:056:09:20:51
Block: 1411200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40378 RingCT/type: yes/0
Extra: 01523f52d8543d8821e833cb09de20573e5002c2d6ba0ec0df3477df76b8ef9a700211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9921b42b01d65de28021caf133fb8795efd184c34edde7badf2f088f2a16dc8 0.600000000000 1899659 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": 1411210, "vin": [ { "gen": { "height": 1411200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9921b42b01d65de28021caf133fb8795efd184c34edde7badf2f088f2a16dc8" } } ], "extra": [ 1, 82, 63, 82, 216, 84, 61, 136, 33, 232, 51, 203, 9, 222, 32, 87, 62, 80, 2, 194, 214, 186, 14, 192, 223, 52, 119, 223, 118, 184, 239, 154, 112, 2, 17, 0, 0, 0, 1, 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