Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfe7c7eea0a037ee89ae766e58ca264517a36fc3d6cb36f3a9f7998fb43936cc

Tx prefix hash: 88f89cbde772c9309d40980827bf5d27a4aa8b2e9c338cae17cc8addb246d40d
Tx public key: cd175f07a7c2f618d58a342098e34b21aab6f0de7c5e266c09966fdaf878121c
Timestamp: 1732778605 Timestamp [UCT]: 2024-11-28 07:23:25 Age [y:d:h:m:s]: 00:037:23:04:36
Block: 1163397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27169 RingCT/type: yes/0
Extra: 01cd175f07a7c2f618d58a342098e34b21aab6f0de7c5e266c09966fdaf878121c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17bb2fdfff7eb242270ce33801d94178e679c01b3e94153641b30866e671b6f7 0.600000000000 1649064 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": 1163407, "vin": [ { "gen": { "height": 1163397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17bb2fdfff7eb242270ce33801d94178e679c01b3e94153641b30866e671b6f7" } } ], "extra": [ 1, 205, 23, 95, 7, 167, 194, 246, 24, 213, 138, 52, 32, 152, 227, 75, 33, 170, 182, 240, 222, 124, 94, 38, 108, 9, 150, 111, 218, 248, 120, 18, 28, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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