Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 931f9be1ca17ff3a7f4e3eb7e7e40924dcbf05568ac1fc70f6cf15252320c780

Tx prefix hash: fd8212af6a52ee80ac24f2b35483e08021235907277c6665fdff7da65e9a60f7
Tx public key: bf35ce3cebe58fe0b54478cec01d50b9f4efb8d974dc6a2ad0c3e3ae5a2cb75c
Timestamp: 1631427904 Timestamp [UCT]: 2021-09-12 06:25:04 Age [y:d:h:m:s]: 03:057:16:24:06
Block: 332125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 816696 RingCT/type: yes/0
Extra: 01bf35ce3cebe58fe0b54478cec01d50b9f4efb8d974dc6a2ad0c3e3ae5a2cb75c021100000013fdc024ec000000000000000000

1 output(s) for total of 48.700390858000 dcy

stealth address amount amount idx
00: 0864008a723279e5830bc76cf78fb0f90c155ff585425b217501422489c95eea 48.700390858000 685998 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": 332135, "vin": [ { "gen": { "height": 332125 } } ], "vout": [ { "amount": 48700390858, "target": { "key": "0864008a723279e5830bc76cf78fb0f90c155ff585425b217501422489c95eea" } } ], "extra": [ 1, 191, 53, 206, 60, 235, 229, 143, 224, 181, 68, 120, 206, 192, 29, 80, 185, 244, 239, 184, 217, 116, 220, 106, 42, 208, 195, 227, 174, 90, 44, 183, 92, 2, 17, 0, 0, 0, 19, 253, 192, 36, 236, 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