Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c7297142b99bafea684cbf1cab7978e5aca5d900674754adb5b50310fa8e9cb

Tx prefix hash: 54b9d9a3da1cf90b1850f39fc1fe67c061d865dbb789f3d739c245dda31cd372
Tx public key: f1f5264da4034ed2d870fd463f65af5e0f515c68ad2128db64ba9f7f9499ba67
Timestamp: 1711893463 Timestamp [UCT]: 2024-03-31 13:57:43 Age [y:d:h:m:s]: 01:009:06:34:36
Block: 990360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267573 RingCT/type: yes/0
Extra: 01f1f5264da4034ed2d870fd463f65af5e0f515c68ad2128db64ba9f7f9499ba6702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f1c089711f23fbe630a7c64fd3d6ef6f3cfb9c19bcd6f162a221a247cb47437 0.600000000000 1450682 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": 990370, "vin": [ { "gen": { "height": 990360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f1c089711f23fbe630a7c64fd3d6ef6f3cfb9c19bcd6f162a221a247cb47437" } } ], "extra": [ 1, 241, 245, 38, 77, 164, 3, 78, 210, 216, 112, 253, 70, 63, 101, 175, 94, 15, 81, 92, 104, 173, 33, 40, 219, 100, 186, 159, 127, 148, 153, 186, 103, 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