Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a118b0be5a92614c4d975149d49e01b9da51dc7d91f3c414446f8bf84a7b37b

Tx prefix hash: 75773147503b8c52d7a757f535eb01276850e5b803bae85168a0659ef2c8bb6f
Tx public key: b97e0e0487f02b7c99db70c49668fb99b49f6104052bd62fa3861ca48393390d
Timestamp: 1718454108 Timestamp [UCT]: 2024-06-15 12:21:48 Age [y:d:h:m:s]: 00:289:09:27:52
Block: 1044753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206789 RingCT/type: yes/0
Extra: 01b97e0e0487f02b7c99db70c49668fb99b49f6104052bd62fa3861ca48393390d02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df44ea1819dc1c351da1fbd305c45fd094486f8062b92cdea5ff5f980c1bbdd7 0.600000000000 1514146 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": 1044763, "vin": [ { "gen": { "height": 1044753 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df44ea1819dc1c351da1fbd305c45fd094486f8062b92cdea5ff5f980c1bbdd7" } } ], "extra": [ 1, 185, 126, 14, 4, 135, 240, 43, 124, 153, 219, 112, 196, 150, 104, 251, 153, 180, 159, 97, 4, 5, 43, 214, 47, 163, 134, 28, 164, 131, 147, 57, 13, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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