Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a23cbcd2227dedcf8bf3262e4697d8ced27ca58b5be526226472999a49ea470

Tx prefix hash: 1f2336e5449cc906da66cee3f05461575d84f3f1461caa15ffd94ae0f64093cc
Tx public key: f438d6aba179be828306a6cfadd3f4fc8fa963cb2d1456ccf820c9c5ac3a5e7c
Timestamp: 1737297340 Timestamp [UCT]: 2025-01-19 14:35:40 Age [y:d:h:m:s]: 00:153:01:13:45
Block: 1200767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109085 RingCT/type: yes/0
Extra: 01f438d6aba179be828306a6cfadd3f4fc8fa963cb2d1456ccf820c9c5ac3a5e7c021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eac74f7278bdfc9b58a8bca1148daefb20b9acbe6e9dbe1301b85e882a33bdfc 0.600000000000 1687412 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": 1200777, "vin": [ { "gen": { "height": 1200767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eac74f7278bdfc9b58a8bca1148daefb20b9acbe6e9dbe1301b85e882a33bdfc" } } ], "extra": [ 1, 244, 56, 214, 171, 161, 121, 190, 130, 131, 6, 166, 207, 173, 211, 244, 252, 143, 169, 99, 203, 45, 20, 86, 204, 248, 32, 201, 197, 172, 58, 94, 124, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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