Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89c9d8bf83ac83482cfc2201f690b194186738730d643c8b37a266e83ba51955

Tx prefix hash: d296bc46f17734d3b90c5e3b88635b3acbbc6ad37911ac5f8474d105745eaeae
Tx public key: 3dc9fd1b9faac2a62faabff441657001f1d5c616b42e112e57cef294db66d036
Timestamp: 1617489421 Timestamp [UCT]: 2021-04-03 22:37:01 Age [y:d:h:m:s]: 03:340:23:44:35
Block: 232677 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1003157 RingCT/type: yes/0
Extra: 013dc9fd1b9faac2a62faabff441657001f1d5c616b42e112e57cef294db66d03602110000001ea1bbccc7000000000000000000

1 output(s) for total of 104.004613453000 dcy

stealth address amount amount idx
00: 3baf3161a2102620c8cf9c42945401a4bb6b6fc61c06fa3d48527caa087afb6c 104.004613453000 483395 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": 232687, "vin": [ { "gen": { "height": 232677 } } ], "vout": [ { "amount": 104004613453, "target": { "key": "3baf3161a2102620c8cf9c42945401a4bb6b6fc61c06fa3d48527caa087afb6c" } } ], "extra": [ 1, 61, 201, 253, 27, 159, 170, 194, 166, 47, 170, 191, 244, 65, 101, 112, 1, 241, 213, 198, 22, 180, 46, 17, 46, 87, 206, 242, 148, 219, 102, 208, 54, 2, 17, 0, 0, 0, 30, 161, 187, 204, 199, 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