Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db303e66048c3dab1b1ac647f8924dc39561e5cf2653818acace381bf5adcdce

Tx prefix hash: 5c4c53d56a2752174c70b6ac703220e6a65ae8ba3e1f7d82fc4aea94e6e21b08
Tx public key: 7c43c667adc449b1fd9a55cd91e59d7927f77e1562415cf2e66f2e39ca374717
Timestamp: 1722110415 Timestamp [UCT]: 2024-07-27 20:00:15 Age [y:d:h:m:s]: 00:232:06:58:46
Block: 1075052 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165923 RingCT/type: yes/0
Extra: 017c43c667adc449b1fd9a55cd91e59d7927f77e1562415cf2e66f2e39ca37471702110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29323d60fb558aba077e6e9a3f312d4cdfdf957a217050c3f604ac2dd43bb781 0.600000000000 1547573 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": 1075062, "vin": [ { "gen": { "height": 1075052 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29323d60fb558aba077e6e9a3f312d4cdfdf957a217050c3f604ac2dd43bb781" } } ], "extra": [ 1, 124, 67, 198, 103, 173, 196, 73, 177, 253, 154, 85, 205, 145, 229, 157, 121, 39, 247, 126, 21, 98, 65, 92, 242, 230, 111, 46, 57, 202, 55, 71, 23, 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