Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8860ec8823effa487d0c3bf15073697a7bb4ef16a0de06d14a86677d4a382e1f

Tx prefix hash: f053e27011c95c458a9d02a922764a41fcc6762e43ad85acb7d48c367ce51ad3
Tx public key: 74c6b99d2eac714c3c6f359ab7f6a5ace6e3442c4550fa45048222f4c647f15a
Timestamp: 1712921686 Timestamp [UCT]: 2024-04-12 11:34:46 Age [y:d:h:m:s]: 00:320:15:30:17
Block: 998850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229231 RingCT/type: yes/0
Extra: 0174c6b99d2eac714c3c6f359ab7f6a5ace6e3442c4550fa45048222f4c647f15a02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c09a3665379aa3de52c35507f2bb5b9e465aa14b86c776c9e04026a93db94b75 0.600000000000 1459316 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": 998860, "vin": [ { "gen": { "height": 998850 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c09a3665379aa3de52c35507f2bb5b9e465aa14b86c776c9e04026a93db94b75" } } ], "extra": [ 1, 116, 198, 185, 157, 46, 172, 113, 76, 60, 111, 53, 154, 183, 246, 165, 172, 230, 227, 68, 44, 69, 80, 250, 69, 4, 130, 34, 244, 198, 71, 241, 90, 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