Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3686e7260be8777f22005952f597c3f1a828edef242c09c283cabe84b11e7cc

Tx prefix hash: c6cc0b789326013f38de1591678dce596fc761e98b262f2f313641247e5dcde2
Tx public key: f124ead6d130ed269e4944b51ea416438e1fdf8458a4b192d68fe13809023455
Timestamp: 1687595959 Timestamp [UCT]: 2023-06-24 08:39:19 Age [y:d:h:m:s]: 01:210:04:01:29
Block: 789167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411549 RingCT/type: yes/0
Extra: 01f124ead6d130ed269e4944b51ea416438e1fdf8458a4b192d68fe13809023455021100000001faf35c9c000000000000000000

1 output(s) for total of 1.489917688000 dcy

stealth address amount amount idx
00: 3f4be60d95796905d6e0e7d8cf80c997a79b7f1e9324bc1dfa867cef6840abae 1.489917688000 1239364 of 0

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": 789177, "vin": [ { "gen": { "height": 789167 } } ], "vout": [ { "amount": 1489917688, "target": { "key": "3f4be60d95796905d6e0e7d8cf80c997a79b7f1e9324bc1dfa867cef6840abae" } } ], "extra": [ 1, 241, 36, 234, 214, 209, 48, 237, 38, 158, 73, 68, 181, 30, 164, 22, 67, 142, 31, 223, 132, 88, 164, 177, 146, 214, 143, 225, 56, 9, 2, 52, 85, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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