Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2641be194a32ef6b88a50cfc660a3f54aefda8d66feae06cb5cc7ab50cf69dac

Tx prefix hash: c3d6e9d678115693c282a3b371cf64ea71aff555bd893f404878ed6ad97902ba
Tx public key: b6c5f95df7339cc8d7bcb4e4b02de990a8aa81160d60dc4dfd2cd2bbdf894a62
Timestamp: 1761684466 Timestamp [UCT]: 2025-10-28 20:47:46 Age [y:d:h:m:s]: 00:011:22:53:07
Block: 1400034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8549 RingCT/type: yes/0
Extra: 01b6c5f95df7339cc8d7bcb4e4b02de990a8aa81160d60dc4dfd2cd2bbdf894a6202110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e43f8d7dd8bf9d57c4dc61a45ef263b4bbd66192ae3105f3080246c6ed37721c 0.600000000000 1888341 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": 1400044, "vin": [ { "gen": { "height": 1400034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e43f8d7dd8bf9d57c4dc61a45ef263b4bbd66192ae3105f3080246c6ed37721c" } } ], "extra": [ 1, 182, 197, 249, 93, 247, 51, 156, 200, 215, 188, 180, 228, 176, 45, 233, 144, 168, 170, 129, 22, 13, 96, 220, 77, 253, 44, 210, 187, 223, 137, 74, 98, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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