Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdc3cce1ab22ad1d731b7886b4056b6021cb2bf1cc4cb547ec41103d8ddc8d8b

Tx prefix hash: 7e16ab5067018c83713224a79c9466d67a272ec8dec79a7890df86da193429cd
Tx public key: f8141907c9616d9064e19fb0d81cc32c82340f51a37876319082bfa66dbf31a0
Timestamp: 1597394420 Timestamp [UCT]: 2020-08-14 08:40:20 Age [y:d:h:m:s]: 05:083:04:25:42
Block: 126412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1278389 RingCT/type: yes/0
Extra: 01f8141907c9616d9064e19fb0d81cc32c82340f51a37876319082bfa66dbf31a0021100000005d81c26c0000000000000000000

1 output(s) for total of 233.961982034000 dcy

stealth address amount amount idx
00: 49d3c4b614eca5a3217121021fa0c95864e4c1164a5d761d5f0a6811706903ad 233.961982034000 213268 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": 126422, "vin": [ { "gen": { "height": 126412 } } ], "vout": [ { "amount": 233961982034, "target": { "key": "49d3c4b614eca5a3217121021fa0c95864e4c1164a5d761d5f0a6811706903ad" } } ], "extra": [ 1, 248, 20, 25, 7, 201, 97, 109, 144, 100, 225, 159, 176, 216, 28, 195, 44, 130, 52, 15, 81, 163, 120, 118, 49, 144, 130, 191, 166, 109, 191, 49, 160, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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