Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b25d477b279d4b53e42395a109b9edc4dffa1d51f6151cfca2604f3e8a5f376

Tx prefix hash: f399e718e6d2f4670f8d8746d45d17d34fc185ed01d5e7a8f291a363f1a78e01
Tx public key: 786d8a9e59001cfb1d3b945ba9e870a2226e3afb4f1ca68d1c328e46e391da3e
Timestamp: 1674435767 Timestamp [UCT]: 2023-01-23 01:02:47 Age [y:d:h:m:s]: 02:085:21:07:52
Block: 680678 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 583018 RingCT/type: yes/0
Extra: 01786d8a9e59001cfb1d3b945ba9e870a2226e3afb4f1ca68d1c328e46e391da3e0211000000025029cbac000000000000000000

1 output(s) for total of 3.409032681000 dcy

stealth address amount amount idx
00: e86bc09216fe4a35b74d243bdb6777ad66718a9c343bfe563f53b51881ce68e8 3.409032681000 1122737 of 0

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": 680688, "vin": [ { "gen": { "height": 680678 } } ], "vout": [ { "amount": 3409032681, "target": { "key": "e86bc09216fe4a35b74d243bdb6777ad66718a9c343bfe563f53b51881ce68e8" } } ], "extra": [ 1, 120, 109, 138, 158, 89, 0, 28, 251, 29, 59, 148, 91, 169, 232, 112, 162, 34, 110, 58, 251, 79, 28, 166, 141, 28, 50, 142, 70, 227, 145, 218, 62, 2, 17, 0, 0, 0, 2, 80, 41, 203, 172, 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