Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5599a2489e34da06ca7f0e72cc98caa846e1e4159a22cc3eba1bd092633eec73

Tx prefix hash: 5ada6fa2b6a7058af70aa16a9f7545c3a31ba31380962c01a1d94aff6c5ccfe0
Tx public key: b788df0a51819986a70787591f1dd736e5400ca7c3e6b88315970c04daa58159
Timestamp: 1711736010 Timestamp [UCT]: 2024-03-29 18:13:30 Age [y:d:h:m:s]: 01:052:17:23:10
Block: 989065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298661 RingCT/type: yes/0
Extra: 01b788df0a51819986a70787591f1dd736e5400ca7c3e6b88315970c04daa5815902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df4a294a378be8df9f179a609c30ddfc79071d56f27f00deddebb4c9c8ac401b 0.600000000000 1449360 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": 989075, "vin": [ { "gen": { "height": 989065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df4a294a378be8df9f179a609c30ddfc79071d56f27f00deddebb4c9c8ac401b" } } ], "extra": [ 1, 183, 136, 223, 10, 81, 129, 153, 134, 167, 7, 135, 89, 31, 29, 215, 54, 229, 64, 12, 167, 195, 230, 184, 131, 21, 151, 12, 4, 218, 165, 129, 89, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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