Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b56e836cebe3bd12b27b1b8cf9a72c834fb0644c1793753f6e3146a06d626d7f

Tx prefix hash: db8231bcc24d901e74c2a74f09e40643e9adcc928c3c27396f89bdad5c0b94e4
Tx public key: 6b06aa276268a157d75d846c2ff822636d1d55ba8250374e129de08023f73273
Timestamp: 1707155564 Timestamp [UCT]: 2024-02-05 17:52:44 Age [y:d:h:m:s]: 01:001:00:19:03
Block: 951060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261750 RingCT/type: yes/0
Extra: 016b06aa276268a157d75d846c2ff822636d1d55ba8250374e129de08023f7327302110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26965e50606b88f8a70587fe55e6c70ae7f45af512b403111aaf12a54e0b3760 0.600000000000 1409772 of 15

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": 951070, "vin": [ { "gen": { "height": 951060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26965e50606b88f8a70587fe55e6c70ae7f45af512b403111aaf12a54e0b3760" } } ], "extra": [ 1, 107, 6, 170, 39, 98, 104, 161, 87, 215, 93, 132, 108, 47, 248, 34, 99, 109, 29, 85, 186, 130, 80, 55, 78, 18, 157, 224, 128, 35, 247, 50, 115, 2, 17, 0, 0, 0, 10, 89, 218, 211, 245, 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