Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64e81034a4324ffe466a9bd1c6a9fcf58fd732267ec907a5ae68bdac51e56582

Tx prefix hash: f03a94113aeac7513355a057286136077f9454774bc148c34197c95c5b9fed58
Tx public key: a74e37923e50285641111a2bb3b6a3459e88dafe3c8c3877c9d5b7fdd64db004
Timestamp: 1683638369 Timestamp [UCT]: 2023-05-09 13:19:29 Age [y:d:h:m:s]: 02:020:14:44:07
Block: 756358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 536869 RingCT/type: yes/0
Extra: 01a74e37923e50285641111a2bb3b6a3459e88dafe3c8c3877c9d5b7fdd64db004021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.913692526000 dcy

stealth address amount amount idx
00: 61a9b6c66c4ac30aa796fe953adaf324bdfbfee1912c344c071d37bf1b0066d7 1.913692526000 1204725 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": 756368, "vin": [ { "gen": { "height": 756358 } } ], "vout": [ { "amount": 1913692526, "target": { "key": "61a9b6c66c4ac30aa796fe953adaf324bdfbfee1912c344c071d37bf1b0066d7" } } ], "extra": [ 1, 167, 78, 55, 146, 62, 80, 40, 86, 65, 17, 26, 43, 179, 182, 163, 69, 158, 136, 218, 254, 60, 140, 56, 119, 201, 213, 183, 253, 214, 77, 176, 4, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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