Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e5f06977968029d72b55253cb2c285f0696789681b1f3bbf44d3d1fb5685519

Tx prefix hash: 26af8ff11f42b8d1dacb03d3ccaa71bb0cafa15e353fccf876158475d49434b8
Tx public key: eae7269a63976c28fd5c24238e38fb36e8bfcf79573efdab0ca31a64d8eec6d3
Timestamp: 1711577099 Timestamp [UCT]: 2024-03-27 22:04:59 Age [y:d:h:m:s]: 01:041:00:53:27
Block: 987741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290303 RingCT/type: yes/0
Extra: 01eae7269a63976c28fd5c24238e38fb36e8bfcf79573efdab0ca31a64d8eec6d302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7ef0168a8a0513b566e6c63f302f423ebb5852ba39e771c4cf2ae540d444d3d 0.600000000000 1448000 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": 987751, "vin": [ { "gen": { "height": 987741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7ef0168a8a0513b566e6c63f302f423ebb5852ba39e771c4cf2ae540d444d3d" } } ], "extra": [ 1, 234, 231, 38, 154, 99, 151, 108, 40, 253, 92, 36, 35, 142, 56, 251, 54, 232, 191, 207, 121, 87, 62, 253, 171, 12, 163, 26, 100, 216, 238, 198, 211, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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