Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cc7e7b64040509b70cf17ee306400ad09f1f8278dd41c89a7e11249345993e8

Tx prefix hash: c23ce616bc27a4cf7bdc528a3df345b2092289969b6c0ab21bb63c4392b6647a
Tx public key: d791e88c3e9054508c4af94e97dc798dccd2f106212f666508cd1eff3a323bfc
Timestamp: 1735624410 Timestamp [UCT]: 2024-12-31 05:53:30 Age [y:d:h:m:s]: 00:172:21:09:13
Block: 1186958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123208 RingCT/type: yes/0
Extra: 01d791e88c3e9054508c4af94e97dc798dccd2f106212f666508cd1eff3a323bfc021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2757430fa27698446c9b1d5e784e4a50629cbe6bc5178a70fd48085d835137d1 0.600000000000 1673443 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": 1186968, "vin": [ { "gen": { "height": 1186958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2757430fa27698446c9b1d5e784e4a50629cbe6bc5178a70fd48085d835137d1" } } ], "extra": [ 1, 215, 145, 232, 140, 62, 144, 84, 80, 140, 74, 249, 78, 151, 220, 121, 141, 204, 210, 241, 6, 33, 47, 102, 101, 8, 205, 30, 255, 58, 50, 59, 252, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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