Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56588791e24910144485b4de50079aef1cd4adc8bfb454425a1174bbf1e9e8e0

Tx prefix hash: b5cc5fc31b6899c62ae62d0809170047b7b1821708801d00b576ca0ff8699623
Tx public key: 7f851c2e4fd65f3f637420748f1032dc9d569c9d04b6d49b4417ff5d6eeba9d0
Timestamp: 1638339196 Timestamp [UCT]: 2021-12-01 06:13:16 Age [y:d:h:m:s]: 02:360:07:33:57
Block: 385890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 775551 RingCT/type: yes/0
Extra: 017f851c2e4fd65f3f637420748f1032dc9d569c9d04b6d49b4417ff5d6eeba9d0021100000005e59f5d07000000000000000000

1 output(s) for total of 32.313694261000 dcy

stealth address amount amount idx
00: dcec00d79231ea9f98a8a947791c33b847a3fb35e865de244c15b0023fea2951 32.313694261000 778641 of 0

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": 385900, "vin": [ { "gen": { "height": 385890 } } ], "vout": [ { "amount": 32313694261, "target": { "key": "dcec00d79231ea9f98a8a947791c33b847a3fb35e865de244c15b0023fea2951" } } ], "extra": [ 1, 127, 133, 28, 46, 79, 214, 95, 63, 99, 116, 32, 116, 143, 16, 50, 220, 157, 86, 156, 157, 4, 182, 212, 155, 68, 23, 255, 93, 110, 235, 169, 208, 2, 17, 0, 0, 0, 5, 229, 159, 93, 7, 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