Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe1f7fd6be17c0fb40ff5884b2683eb379e75e15601f0d700e69904017cd1ce6

Tx prefix hash: 02a81de99e839001e5d8b8c767220dffe7a78047facf100cd8e61ea762136ed3
Tx public key: 92fef17c65de0bc59e3b548a7b0f5f35aae3f7c9256896819391bc18655fb87b
Timestamp: 1751006696 Timestamp [UCT]: 2025-06-27 06:44:56 Age [y:d:h:m:s]: 00:146:01:16:33
Block: 1313697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102409 RingCT/type: yes/0
Extra: 0192fef17c65de0bc59e3b548a7b0f5f35aae3f7c9256896819391bc18655fb87b021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46b5ba7b4c66f8bbfa92d7696989f815cbfe11b1b6a14435dcf9de5df7b0d46c 0.600000000000 1801340 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": 1313707, "vin": [ { "gen": { "height": 1313697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46b5ba7b4c66f8bbfa92d7696989f815cbfe11b1b6a14435dcf9de5df7b0d46c" } } ], "extra": [ 1, 146, 254, 241, 124, 101, 222, 11, 197, 158, 59, 84, 138, 123, 15, 95, 53, 170, 227, 247, 201, 37, 104, 150, 129, 147, 145, 188, 24, 101, 95, 184, 123, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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