Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c7c60d1a78b1941f38482b78f42bb0fdab7163b7f91e7965e9d3bd4a14c8795

Tx prefix hash: 793dd91fc15cb3b43d18d4386e1731c3998e3fc393bb8f36dcd36139785d7ece
Tx public key: 8901c68ce8a76f436146d41534eacc01a8da76129ce0a05f55ffae49f4fc41ba
Timestamp: 1709359596 Timestamp [UCT]: 2024-03-02 06:06:36 Age [y:d:h:m:s]: 01:110:15:55:41
Block: 969347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339982 RingCT/type: yes/0
Extra: 018901c68ce8a76f436146d41534eacc01a8da76129ce0a05f55ffae49f4fc41ba0211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9aa448687f78a4f0fbfe1f55bb8d137e4c19138d30c4d0480e8b0ffb961b9e00 0.600000000000 1429176 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": 969357, "vin": [ { "gen": { "height": 969347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9aa448687f78a4f0fbfe1f55bb8d137e4c19138d30c4d0480e8b0ffb961b9e00" } } ], "extra": [ 1, 137, 1, 198, 140, 232, 167, 111, 67, 97, 70, 212, 21, 52, 234, 204, 1, 168, 218, 118, 18, 156, 224, 160, 95, 85, 255, 174, 73, 244, 252, 65, 186, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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