Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a28ac7a31a8c1c946d505754ffceac1a81e22eff55a64961c6c37c2cac94b10

Tx prefix hash: 1d3f6d1438dfaff5c38ab897bc850eea907cbecc77c520b1a3150dee621e841f
Tx public key: ac3bfddd9669804463e5d10ca1dcb8f013e1e27b8baadb0947171e45ed8e1144
Timestamp: 1677786425 Timestamp [UCT]: 2023-03-02 19:47:05 Age [y:d:h:m:s]: 01:323:23:16:38
Block: 708466 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492467 RingCT/type: yes/0
Extra: 01ac3bfddd9669804463e5d10ca1dcb8f013e1e27b8baadb0947171e45ed8e11440211000000015029cbac000000000000000000

1 output(s) for total of 2.757769376000 dcy

stealth address amount amount idx
00: bacaeb179f8924ea29acb5fd9a3fbbaf56cbba710973908263c19a9b15212f29 2.757769376000 1152361 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": 708476, "vin": [ { "gen": { "height": 708466 } } ], "vout": [ { "amount": 2757769376, "target": { "key": "bacaeb179f8924ea29acb5fd9a3fbbaf56cbba710973908263c19a9b15212f29" } } ], "extra": [ 1, 172, 59, 253, 221, 150, 105, 128, 68, 99, 229, 209, 12, 161, 220, 184, 240, 19, 225, 226, 123, 139, 170, 219, 9, 71, 23, 30, 69, 237, 142, 17, 68, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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