Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5282e60758c50f8e797f3553727d126de8ee752e6ac1a49765b912a3aad79f0c

Tx prefix hash: 7f61b07c231abd6d2de1f64ab4ed19217daca894589055035f625d0af73bf3b9
Tx public key: 6c890a3992482994e2a9a1447784a3fb3212ed1f7506a0b6d96c0901c9177846
Timestamp: 1737730872 Timestamp [UCT]: 2025-01-24 15:01:12 Age [y:d:h:m:s]: 00:144:09:45:46
Block: 1204353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102949 RingCT/type: yes/0
Extra: 016c890a3992482994e2a9a1447784a3fb3212ed1f7506a0b6d96c0901c9177846021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df579f68a91789e276d6df924470857d0847b24446b4bb2f65430c794b7bb8b2 0.600000000000 1691038 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": 1204363, "vin": [ { "gen": { "height": 1204353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df579f68a91789e276d6df924470857d0847b24446b4bb2f65430c794b7bb8b2" } } ], "extra": [ 1, 108, 137, 10, 57, 146, 72, 41, 148, 226, 169, 161, 68, 119, 132, 163, 251, 50, 18, 237, 31, 117, 6, 160, 182, 217, 108, 9, 1, 201, 23, 120, 70, 2, 17, 0, 0, 0, 1, 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