Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0558376600c7687024e67820e97656fee5f5b0439f0b9c3059f5807d4e6d9b6e

Tx prefix hash: bfb84d2b6fdb80ba6214868a161f3e3d3fb88e927748211f61405c11f8d84042
Tx public key: 864cc90b3c895298315f22b36d274da986ce3fb831349e60d6a4cc048e28934c
Timestamp: 1735335135 Timestamp [UCT]: 2024-12-27 21:32:15 Age [y:d:h:m:s]: 00:083:23:41:07
Block: 1184557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59819 RingCT/type: yes/0
Extra: 01864cc90b3c895298315f22b36d274da986ce3fb831349e60d6a4cc048e28934c021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5dd09bacd40b1442a0a75b052ad1cb042554dbe80a82566fccd32152c58c34c 0.600000000000 1671014 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": 1184567, "vin": [ { "gen": { "height": 1184557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5dd09bacd40b1442a0a75b052ad1cb042554dbe80a82566fccd32152c58c34c" } } ], "extra": [ 1, 134, 76, 201, 11, 60, 137, 82, 152, 49, 95, 34, 179, 109, 39, 77, 169, 134, 206, 63, 184, 49, 52, 158, 96, 214, 164, 204, 4, 142, 40, 147, 76, 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