Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43a55e4ab5c7bd60bfa698755371bbb3b7f082df19e5ab49bfb954261306b910

Tx prefix hash: 003d4cb13004f97f12b39414c84e2a792b8fc5057f22688ff7d1d5ae007a0c2c
Tx public key: f1dc0f388a58faa5b4f24d6bb504fc7715ff857098c3d7f538eee6f43b325a16
Timestamp: 1762203656 Timestamp [UCT]: 2025-11-03 21:00:56 Age [y:d:h:m:s]: 00:007:16:28:50
Block: 1404316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5511 RingCT/type: yes/0
Extra: 01f1dc0f388a58faa5b4f24d6bb504fc7715ff857098c3d7f538eee6f43b325a160211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa535a6688092fc967f0f21a378b902b0a8bdc404eafe3f8b33caf665bf383af 0.600000000000 1892673 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": 1404326, "vin": [ { "gen": { "height": 1404316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa535a6688092fc967f0f21a378b902b0a8bdc404eafe3f8b33caf665bf383af" } } ], "extra": [ 1, 241, 220, 15, 56, 138, 88, 250, 165, 180, 242, 77, 107, 181, 4, 252, 119, 21, 255, 133, 112, 152, 195, 215, 245, 56, 238, 230, 244, 59, 50, 90, 22, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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