Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df3e72d97ae870649e37eaa7f2d576f9cf97a2fa7159e6683fb3559701219a1a

Tx prefix hash: 7589a5adfe4820a3f4ea7ca03c7d8175f5c4a45c94396eacf53ddef939fc89d7
Tx public key: 8763c9159e72efa63f9ebf07ede770798460b40f8a4cb368f3cb40772c6459a5
Timestamp: 1750717653 Timestamp [UCT]: 2025-06-23 22:27:33 Age [y:d:h:m:s]: 00:149:08:25:06
Block: 1311391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104675 RingCT/type: yes/0
Extra: 018763c9159e72efa63f9ebf07ede770798460b40f8a4cb368f3cb40772c6459a502110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f70f68f264ff6eaa304b7c42f631e0b3fc4c42ac25dbf8194d73a7292982dd2a 0.600000000000 1799018 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": 1311401, "vin": [ { "gen": { "height": 1311391 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f70f68f264ff6eaa304b7c42f631e0b3fc4c42ac25dbf8194d73a7292982dd2a" } } ], "extra": [ 1, 135, 99, 201, 21, 158, 114, 239, 166, 63, 158, 191, 7, 237, 231, 112, 121, 132, 96, 180, 15, 138, 76, 179, 104, 243, 203, 64, 119, 44, 100, 89, 165, 2, 17, 0, 0, 0, 3, 67, 132, 109, 102, 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