Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51cb5223a627e47f4119218ecbbb215ff2cab4150d431198d386d1806c827209

Tx prefix hash: 1d9c3d9336c81c4b9807737994739dd582f37a00466f00f2d1d962f226e6bd7a
Tx public key: 2ed1fed468cf97d0d621942f6de963c1a573a6da1e4878ff5d8f6051f84654e2
Timestamp: 1722564031 Timestamp [UCT]: 2024-08-02 02:00:31 Age [y:d:h:m:s]: 00:234:22:40:24
Block: 1078811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167797 RingCT/type: yes/0
Extra: 012ed1fed468cf97d0d621942f6de963c1a573a6da1e4878ff5d8f6051f84654e202110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3a788b969a3f03a004fe5d068cecda055c951d0cd88f18e7248e645fdbea62a 0.600000000000 1551502 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": 1078821, "vin": [ { "gen": { "height": 1078811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3a788b969a3f03a004fe5d068cecda055c951d0cd88f18e7248e645fdbea62a" } } ], "extra": [ 1, 46, 209, 254, 212, 104, 207, 151, 208, 214, 33, 148, 47, 109, 233, 99, 193, 165, 115, 166, 218, 30, 72, 120, 255, 93, 143, 96, 81, 248, 70, 84, 226, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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