Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 708dfc2481412cf933ad0096f4fbb541562300a7d1c147afb365735a95e88b4b

Tx prefix hash: 3273fe5a0baaf93ea06695a9776297d438d160cd0876f91817e6810f1a2b824d
Tx public key: dbcbdb6044b72782d2a5bc6beb1ea485e27f0f324fcf1c48daae1e219fe79f24
Timestamp: 1754461955 Timestamp [UCT]: 2025-08-06 06:32:35 Age [y:d:h:m:s]: 00:057:13:17:28
Block: 1341303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 40061 RingCT/type: yes/0
Extra: 01dbcbdb6044b72782d2a5bc6beb1ea485e27f0f324fcf1c48daae1e219fe79f24021100000003ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f9410bc7468f3284ad05516b453e26ff1d4122ebe4ea4598b484ec1a6bcc8b1 0.600000000000 1829126 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": 1341313, "vin": [ { "gen": { "height": 1341303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f9410bc7468f3284ad05516b453e26ff1d4122ebe4ea4598b484ec1a6bcc8b1" } } ], "extra": [ 1, 219, 203, 219, 96, 68, 183, 39, 130, 210, 165, 188, 107, 235, 30, 164, 133, 226, 127, 15, 50, 79, 207, 28, 72, 218, 174, 30, 33, 159, 231, 159, 36, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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