Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed5f1a865a87aa1936d21a49363ed84ac7ef5f270d94c72e0e1fbd029b1ffc4f

Tx prefix hash: 5e147d4ff8cde30a635e59995f504f676bae98a67bdd8265c454c6bca9e2c343
Tx public key: 5c358ee042dc29c462c17d2caed24b34b44eee0936427bbc973f9c44b3dd20b9
Timestamp: 1709369740 Timestamp [UCT]: 2024-03-02 08:55:40 Age [y:d:h:m:s]: 00:332:18:04:44
Block: 969429 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237931 RingCT/type: yes/0
Extra: 015c358ee042dc29c462c17d2caed24b34b44eee0936427bbc973f9c44b3dd20b90211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b65a18bcab283cab68b5dca49eb6eed822f4cc37588937136e84ff4dc6ea430 0.600000000000 1429258 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": 969439, "vin": [ { "gen": { "height": 969429 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b65a18bcab283cab68b5dca49eb6eed822f4cc37588937136e84ff4dc6ea430" } } ], "extra": [ 1, 92, 53, 142, 224, 66, 220, 41, 196, 98, 193, 125, 44, 174, 210, 75, 52, 180, 78, 238, 9, 54, 66, 123, 188, 151, 63, 156, 68, 179, 221, 32, 185, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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