Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17518d2ded122519318df6f76bc18911be138dee28fb6d3de190ad3f3da15b1b

Tx prefix hash: 340b6146d0ec336dd48c99257492f0ab4bb4d006f580cc567b831cf7b5926dc3
Tx public key: 47c9ed2b7cf870bdc65f7e9a0c1d1b60c9b2903f635099c929415d37a38fa0eb
Timestamp: 1723675482 Timestamp [UCT]: 2024-08-14 22:44:42 Age [y:d:h:m:s]: 01:085:06:28:23
Block: 1088027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319407 RingCT/type: yes/0
Extra: 0147c9ed2b7cf870bdc65f7e9a0c1d1b60c9b2903f635099c929415d37a38fa0eb02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38dd3436f5ebbf924b31eb0038d3a051254732a00a641a6cc127581d140813ff 0.600000000000 1562638 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": 1088037, "vin": [ { "gen": { "height": 1088027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38dd3436f5ebbf924b31eb0038d3a051254732a00a641a6cc127581d140813ff" } } ], "extra": [ 1, 71, 201, 237, 43, 124, 248, 112, 189, 198, 95, 126, 154, 12, 29, 27, 96, 201, 178, 144, 63, 99, 80, 153, 201, 41, 65, 93, 55, 163, 143, 160, 235, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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