Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60908287ee97ca7266120182a8b115dc327c4cdd949f9c5a92e3961eba914eb9

Tx prefix hash: 04cea1291ea091e81d30352862c4fb1ffa8477b51b7812ce18f1f59421da4e08
Tx public key: e8ce7cd2d2e4692e6be915825b5b7490fca723370e180987f9b178a97212d5d4
Timestamp: 1695359504 Timestamp [UCT]: 2023-09-22 05:11:44 Age [y:d:h:m:s]: 01:111:00:05:17
Block: 853466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340633 RingCT/type: yes/0
Extra: 01e8ce7cd2d2e4692e6be915825b5b7490fca723370e180987f9b178a97212d5d40211000000084b8f5122000000000000000000

1 output(s) for total of 0.912317964000 dcy

stealth address amount amount idx
00: 2f5a967cf550114635efd96abd5cc9cabd4c89395afe398359b53ec5aa3f1599 0.912317964000 1307372 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": 853476, "vin": [ { "gen": { "height": 853466 } } ], "vout": [ { "amount": 912317964, "target": { "key": "2f5a967cf550114635efd96abd5cc9cabd4c89395afe398359b53ec5aa3f1599" } } ], "extra": [ 1, 232, 206, 124, 210, 210, 228, 105, 46, 107, 233, 21, 130, 91, 91, 116, 144, 252, 167, 35, 55, 14, 24, 9, 135, 249, 177, 120, 169, 114, 18, 213, 212, 2, 17, 0, 0, 0, 8, 75, 143, 81, 34, 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