Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fcb72ddd00025271c79eab78808fa82d0059b57fb66db38bccff817d0176e254

Tx prefix hash: 8a81bd4d87103ab89a6d85e23589bea4d9784b335be43702e7f362825d866249
Tx public key: eb612a12e9c2a15764a43b1cda5c9b74740469286e5ab98d49f6a253bad919b8
Timestamp: 1746399825 Timestamp [UCT]: 2025-05-04 23:03:45 Age [y:d:h:m:s]: 00:200:02:33:47
Block: 1275899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140719 RingCT/type: yes/0
Extra: 01eb612a12e9c2a15764a43b1cda5c9b74740469286e5ab98d49f6a253bad919b80211000000091f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 254dce4e729dcb9b9960407e73a25275871ebc65c5ca67d2120600b1398a42a4 0.600000000000 1763214 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": 1275909, "vin": [ { "gen": { "height": 1275899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "254dce4e729dcb9b9960407e73a25275871ebc65c5ca67d2120600b1398a42a4" } } ], "extra": [ 1, 235, 97, 42, 18, 233, 194, 161, 87, 100, 164, 59, 28, 218, 92, 155, 116, 116, 4, 105, 40, 110, 90, 185, 141, 73, 246, 162, 83, 186, 217, 25, 184, 2, 17, 0, 0, 0, 9, 31, 144, 81, 122, 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