Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 917fbe4a1e0404bfc6ba5c1c5776737517ced4f701363da731961a7c6dc48d11

Tx prefix hash: 5e56b8d9481aceec55c1f6473d3d1317561bf50d0b0864780d6c12e8db05825d
Tx public key: cd69f2f1f6de9e4e20e5108b29b749812017558bad71f2c7f2a616a9d2811433
Timestamp: 1765137716 Timestamp [UCT]: 2025-12-07 20:01:56 Age [y:d:h:m:s]: 00:014:00:48:51
Block: 1428636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 10040 RingCT/type: yes/0
Extra: 01cd69f2f1f6de9e4e20e5108b29b749812017558bad71f2c7f2a616a9d28114330211000000057b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5eabdf20c32ebf6628bdcd8b11f4e3be576964f002b0392549b2c42b30aebe6a 0.600000000000 1917357 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": 1428646, "vin": [ { "gen": { "height": 1428636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5eabdf20c32ebf6628bdcd8b11f4e3be576964f002b0392549b2c42b30aebe6a" } } ], "extra": [ 1, 205, 105, 242, 241, 246, 222, 158, 78, 32, 229, 16, 139, 41, 183, 73, 129, 32, 23, 85, 139, 173, 113, 242, 199, 242, 166, 22, 169, 210, 129, 20, 51, 2, 17, 0, 0, 0, 5, 123, 30, 81, 172, 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