Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 399314ecb4f93a08eadd5d08a7de52a4549658e5310147e8fb32224c706b79c4

Tx prefix hash: 233da31c68f135ce259b0fab565caa77e2518b80a23fc4a20e6b8e33556590bb
Tx public key: b2495fdfa103f3b7bae62c795f6f8b2235cb42c63faf06d6ddd4a45432c7114c
Timestamp: 1746194679 Timestamp [UCT]: 2025-05-02 14:04:39 Age [y:d:h:m:s]: 00:202:21:57:16
Block: 1274203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142731 RingCT/type: yes/0
Extra: 01b2495fdfa103f3b7bae62c795f6f8b2235cb42c63faf06d6ddd4a45432c7114c0211000000061f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f5cc18ce1743b2107993fd6806d1c174fda8511b2567822be3819838b92f4fd 0.600000000000 1761494 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": 1274213, "vin": [ { "gen": { "height": 1274203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f5cc18ce1743b2107993fd6806d1c174fda8511b2567822be3819838b92f4fd" } } ], "extra": [ 1, 178, 73, 95, 223, 161, 3, 243, 183, 186, 230, 44, 121, 95, 111, 139, 34, 53, 203, 66, 198, 63, 175, 6, 214, 221, 212, 164, 84, 50, 199, 17, 76, 2, 17, 0, 0, 0, 6, 31, 144, 81, 122, 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