Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f585944bcb659fc62f513a3f0a2bf7db74e9a1b9e9b20af5eef718c46e4b0f9e

Tx prefix hash: 8463555f40f6e149642a7755fe519fa5518f2ac4ee37e0f1cc8ab045473cf96a
Tx public key: e8bba3375d0f1c84589464cb1cc57ea7ef87d848b3d1f2476b87ca0d2ae4e32f
Timestamp: 1714071055 Timestamp [UCT]: 2024-04-25 18:50:55 Age [y:d:h:m:s]: 00:245:21:00:23
Block: 1008390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175997 RingCT/type: yes/0
Extra: 01e8bba3375d0f1c84589464cb1cc57ea7ef87d848b3d1f2476b87ca0d2ae4e32f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9a8d6daa36838590bd5a8222d78ae0379e8bf85f18ae440bfe1e31d47b7576f 0.600000000000 1469860 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": 1008400, "vin": [ { "gen": { "height": 1008390 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9a8d6daa36838590bd5a8222d78ae0379e8bf85f18ae440bfe1e31d47b7576f" } } ], "extra": [ 1, 232, 187, 163, 55, 93, 15, 28, 132, 88, 148, 100, 203, 28, 197, 126, 167, 239, 135, 216, 72, 179, 209, 242, 71, 107, 135, 202, 13, 42, 228, 227, 47, 2, 17, 0, 0, 0, 1, 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