Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49c860f39df5382609608df749d081a79543615a5e4af1c62f867b1a7b532a33

Tx prefix hash: d4cc36357e7efc78ba15381ad2b4d04b967fe70dcfb7b0b9e98d973a577b80d9
Tx public key: 02024c381efce9460fb914af5ab6219703d6619f0202354ac241e57d1d41d402
Timestamp: 1735013737 Timestamp [UTC]: 2024-12-24 04:15:37 Age [y:d:h:m:s]: 01:041:01:12:49
Block: 1181916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287644 RingCT/type: yes/0
Extra: 0102024c381efce9460fb914af5ab6219703d6619f0202354ac241e57d1d41d402021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: aa68a5dab13bd423a659c40cf370e7250cb79831b6af3c0bdd2dd6cf739625b8 0.000600000000 1668345 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 dinastycoin-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": 1181926, "vin": [ { "gen": { "height": 1181916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa68a5dab13bd423a659c40cf370e7250cb79831b6af3c0bdd2dd6cf739625b8" } } ], "extra": [ 1, 2, 2, 76, 56, 30, 252, 233, 70, 15, 185, 20, 175, 90, 182, 33, 151, 3, 214, 97, 159, 2, 2, 53, 74, 194, 65, 229, 125, 29, 65, 212, 2, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369