Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f41ff078cabcc82ac7a28907c72a4881543c9facd34cb19238f645c2ffaee978

Tx prefix hash: 98eed1a84c7680cefcf7e3dd58fb520f6057061c246c82aea528b4255fcae1b7
Tx public key: d28b5c049f798d6f6122acc8d1c3b932ffe34d265c29172ab7db8d7d77fa1256
Timestamp: 1746959140 Timestamp [UCT]: 2025-05-11 10:25:40 Age [y:d:h:m:s]: 00:192:15:49:44
Block: 1280529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135408 RingCT/type: yes/0
Extra: 01d28b5c049f798d6f6122acc8d1c3b932ffe34d265c29172ab7db8d7d77fa125602110000000c9f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e34784f6d80a513246422e82079ab1a528700e0d889809a09f7f2338ba953fcd 0.600000000000 1767916 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": 1280539, "vin": [ { "gen": { "height": 1280529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e34784f6d80a513246422e82079ab1a528700e0d889809a09f7f2338ba953fcd" } } ], "extra": [ 1, 210, 139, 92, 4, 159, 121, 141, 111, 97, 34, 172, 200, 209, 195, 185, 50, 255, 227, 77, 38, 92, 41, 23, 42, 183, 219, 141, 125, 119, 250, 18, 86, 2, 17, 0, 0, 0, 12, 159, 159, 230, 140, 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