Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf93656a722fb361865bc23c4fa4e92a68ac8d890d11e89847a0550b1055444e

Tx prefix hash: 2e21470e40ae43ec2d037b5bb13f8dbf1a15f430abcfea0b8c9a387bd10e0358
Tx public key: 3ec36f57599b5f5262ae4711962923705a4b254b6306bb2c8319cedf0683ebdf
Timestamp: 1750788354 Timestamp [UCT]: 2025-06-24 18:05:54 Age [y:d:h:m:s]: 00:198:11:31:12
Block: 1311982 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139857 RingCT/type: yes/0
Extra: 013ec36f57599b5f5262ae4711962923705a4b254b6306bb2c8319cedf0683ebdf021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b2adbfe16d9b84641e3b904e10c81699d39909dbe3b7da103a8b166f6d06893 0.600000000000 1799613 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": 1311992, "vin": [ { "gen": { "height": 1311982 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b2adbfe16d9b84641e3b904e10c81699d39909dbe3b7da103a8b166f6d06893" } } ], "extra": [ 1, 62, 195, 111, 87, 89, 155, 95, 82, 98, 174, 71, 17, 150, 41, 35, 112, 90, 75, 37, 75, 99, 6, 187, 44, 131, 25, 206, 223, 6, 131, 235, 223, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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