Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6424e76db751ca0003ce6f92415108c5b1fab83f9dce623cf4cf447ea5a5495

Tx prefix hash: b98bfee61c44b483d71efcc0a406c6927ec6e6d5c5e3c5c5a56f6bb4d55a4bb9
Tx public key: f8984ca04473ae6267fac6b0794f43e2ecd32f69ab0054d894c580be92836926
Timestamp: 1751487861 Timestamp [UCT]: 2025-07-02 20:24:21 Age [y:d:h:m:s]: 00:130:01:40:54
Block: 1317460 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91197 RingCT/type: yes/0
Extra: 01f8984ca04473ae6267fac6b0794f43e2ecd32f69ab0054d894c580be92836926021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bf25521b465a4d83fed128ec829af1ec8d6de69300438a7b7514fc4f9a3f6ba 0.600000000000 1805127 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": 1317470, "vin": [ { "gen": { "height": 1317460 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bf25521b465a4d83fed128ec829af1ec8d6de69300438a7b7514fc4f9a3f6ba" } } ], "extra": [ 1, 248, 152, 76, 160, 68, 115, 174, 98, 103, 250, 198, 176, 121, 79, 67, 226, 236, 211, 47, 105, 171, 0, 84, 216, 148, 197, 128, 190, 146, 131, 105, 38, 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