Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f10d9543c20230b9971a5ab5175e4e540dc687a9fe4e33b5e4aa5ae429c3d8c

Tx prefix hash: 3273c96fa5d297630c993c5d97a15253d1e22f55e45dd2a70ece3c56db5253ca
Tx public key: 967c782e6d9a18bcb5d8b39863956fd2dab8737f5f7018c742ace56f8cf201ec
Timestamp: 1744916770 Timestamp [UCT]: 2025-04-17 19:06:10 Age [y:d:h:m:s]: 00:267:20:02:39
Block: 1263605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189238 RingCT/type: yes/0
Extra: 01967c782e6d9a18bcb5d8b39863956fd2dab8737f5f7018c742ace56f8cf201ec021100000004dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee44035bfc37ba1e0a93ee63b9ccd54bcef283415234f113fa98b4135a2eaee6 0.600000000000 1750796 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": 1263615, "vin": [ { "gen": { "height": 1263605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee44035bfc37ba1e0a93ee63b9ccd54bcef283415234f113fa98b4135a2eaee6" } } ], "extra": [ 1, 150, 124, 120, 46, 109, 154, 24, 188, 181, 216, 179, 152, 99, 149, 111, 210, 218, 184, 115, 127, 95, 112, 24, 199, 66, 172, 229, 111, 140, 242, 1, 236, 2, 17, 0, 0, 0, 4, 219, 181, 113, 193, 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