Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df358650c6ed1bc5fc11b6c0716b299c26952e4a92014e09d51c21f397a7b5e3

Tx prefix hash: 61979b4068ad47fa65433adcda15a0bc05e7bca53263624886f9ae98cc370947
Tx public key: 8d99128a05bd07589e6aa104897d942fc2a91f5b1edc6f075c429fe6c9998715
Timestamp: 1750118551 Timestamp [UCT]: 2025-06-17 00:02:31 Age [y:d:h:m:s]: 00:229:11:58:53
Block: 1306577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161732 RingCT/type: yes/0
Extra: 018d99128a05bd07589e6aa104897d942fc2a91f5b1edc6f075c429fe6c999871502110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09b7fee3aac5998534b9d06f696117a9e919366aa7566e7fe6e6faa18e2d1f87 0.600000000000 1794184 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": 1306587, "vin": [ { "gen": { "height": 1306577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09b7fee3aac5998534b9d06f696117a9e919366aa7566e7fe6e6faa18e2d1f87" } } ], "extra": [ 1, 141, 153, 18, 138, 5, 189, 7, 88, 158, 106, 161, 4, 137, 125, 148, 47, 194, 169, 31, 91, 30, 220, 111, 7, 92, 66, 159, 230, 201, 153, 135, 21, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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