Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab9c78db1cea26f4d4490f1386fff823877efeb5e3aa08d57a3d55fa84f86395

Tx prefix hash: c171c5c965855e43c842b920b5188c3c2453999dfeff90e81c0bce003dca5a77
Tx public key: 662cf4f64fd5529e3e3d6189e35d6fd93e48d1e6ccd5e0cfd5db4aec3dcc1d27
Timestamp: 1714699683 Timestamp [UCT]: 2024-05-03 01:28:03 Age [y:d:h:m:s]: 01:187:20:48:36
Block: 1013624 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392881 RingCT/type: yes/0
Extra: 01662cf4f64fd5529e3e3d6189e35d6fd93e48d1e6ccd5e0cfd5db4aec3dcc1d270211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1ef59b021dbc23d9e1a4743bb8eb39269f0e525b6ebe040d8a108ddd0bc5446 0.600000000000 1476491 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": 1013634, "vin": [ { "gen": { "height": 1013624 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1ef59b021dbc23d9e1a4743bb8eb39269f0e525b6ebe040d8a108ddd0bc5446" } } ], "extra": [ 1, 102, 44, 244, 246, 79, 213, 82, 158, 62, 61, 97, 137, 227, 93, 111, 217, 62, 72, 209, 230, 204, 213, 224, 207, 213, 219, 74, 236, 61, 204, 29, 39, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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